On Mon, 07 Apr 2014 00:47:18 -0400 (EDT), Chris Bannister wrote:
>
> TBH, I didn't see any evidence of a broken thread. Mutt shows a broken
> thread with an asterisk in the arrow symbol.
>
> A poster shouldn't have to jump through hoops to make the archives look
> good, IMHO.
>
> IOW, how the ar
On Sun, Apr 06, 2014 at 10:06:04AM -0400, Stephen Powell wrote:
> On Sat, 05 Apr 2014 20:55:12 -0400 (EDT), Tom Furie wrote:
> >
> > Thread wasn't broken here. The References: header in Robert's mail
> > indicates that it was indeed a reply (to his original post on this
> > thread).
>
> Perhaps I
On Sat, 05 Apr 2014 20:55:12 -0400 (EDT), Tom Furie wrote:
>
> Thread wasn't broken here. The References: header in Robert's mail
> indicates that it was indeed a reply (to his original post on this
> thread).
Perhaps I need to explain what I mean by "broken thread".
The original post was in Marc
On Sat, Apr 05, 2014 at 08:05:09PM -0400, Stephen Powell wrote:
> First of all, you've broken the thread. The thread was broken once
> already by the March / April forced break at the end of the month.
> You can't help that. But this time, you've broken it yourself by
> starting a new thread.
T
On Sat, 05 Apr 2014 13:26:44 -0400 (EDT), Robert Holtzman wrote:
>
> For a while it looked like a bad cable as I was able to connect on a
> different one from the same router. The connection lasted long enough to
> d/l an update. Then I closed the connection. Today none of the cables
> from the ro
On Sun, Mar 30, 2014 at 10:31:54PM -0700, Robert Holtzman wrote:
> I seem to remember this happening after an update but I'm not positive.
> It did work before. My wireless connection continues to work.
>
> Looked at the usual suspects, /etc/ network/interfaces, /etc/resolv.conf,
> etc but everyt
6 matches
Mail list logo
