DISCLAIMER & WARNING: Threading may still be incorrect. Tempting as
this message might be, if incorrect threading upsets you please stop
reading. =8~)
To my understanding In-Reply-To and References were added to the
earlier message correctly but the list server put them in the Web
b
t have deleted the message. Using
> > tools available, in Debian or otherwise, can you reply with correct
> > threading?
>
> Well, besides the aspect of software availablilty, it is a a matter of
> knowing the message id of the mail to which you want to refer.
> Then yo
se, can you reply with correct
> threading?
Well, besides the aspect of software availablilty, it is a a matter of
knowing the message id of the mail to which you want to refer.
Then you have to put it into a "In-Reply-To:" header or a "References:"
header.
The message ids
ols available, in Debian or otherwise, can you reply with correct
> threading? If so, please outline the procedure.
Under the message, you'll see a section headed "Reply to:". Clicking on
one of the links in that section (assuming your browser is correctly
configured to op
Suppose you read a message in the Web based archive and it is no
longer in your mailer. Either you weren't subscribed when the message
was sent or you were subscribed but have deleted the message. Using
tools available, in Debian or otherwise, can you reply with correct
threading?
On Mon 29 Jul 2019 at 06:15:42 (-0700), pe...@easthope.ca wrote:
> From: Reco
> Date: Tue, 23 Jul 2019 19:26:13 +0300
> > In short, please consider using another e-mail client.
>
> I compose the reply from the debian-user Web page. I don't know of a
> MUA capable of reading a page and composing
From: Reco
Date: Tue, 23 Jul 2019 19:26:13 +0300
> In short, please consider using another e-mail client.
I compose the reply from the debian-user Web page. I don't know of a
MUA capable of reading a page and composing a reply to it.
The boilerplate for a reply to a debian page is composed wit
pe...@easthope.ca writes:
* From: Reco recovery...@enotuniq.net
* Date: Mon, 22 Jul 2019 17:35:27 +0300
> You're breaking threading. Just a friendly note.
I've been adding References manually. By "breaking" do you refer to
omission of older refere
On Tue 23 Jul 2019 at 08:56:36 (-0700), pe...@easthope.ca wrote:
> In future I'll make more effort with the references. Beyond 3 or 4 it
> can be tedious.
If you're typing (or pasting) the references, I would just add
the In-Reply-To instead. That way, you can Cut/Copy the original's
Messa
On Tue, 23 Jul 2019 12:28:50 -0400
Greg Wooledge wrote:
Hello Greg,
>We may be seeing different symptoms as a result of *whatever* Peter is
>doing, depending on how each individual mail transport agent and each
>mail user agent deals with the incoming mess.
Indeed.
I looked up his MUA (Oberon,
On Tue, Jul 23, 2019 at 05:22:44PM +0100, Brad Rogers wrote:
> On Tue, 23 Jul 2019 12:16:31 -0400
> Greg Wooledge wrote:
>
> Hello Greg,
>
> >You need to add "In-Reply-To:" as well. And stop doing whatever it is
> >you're doing that puts NUL bytes in your "* From:" lines. Or simply
> >drop
Hi.
On Tue, Jul 23, 2019 at 08:56:36AM -0700, pe...@easthope.ca wrote:
> * From: Reco ?recovery...@enotuniq.net?
> * Date: Mon, 22 Jul 2019 17:35:27 +0300
> > You're breaking threading. Just a friendly note.
>
> I've been adding References manually.
On Tue, 23 Jul 2019 12:16:31 -0400
Greg Wooledge wrote:
Hello Greg,
>You need to add "In-Reply-To:" as well. And stop doing whatever it is
>you're doing that puts NUL bytes in your "* From:" lines. Or simply
>drop those lines altogethe
I /think/ they're tab characters. At least, that see
On Tue, Jul 23, 2019 at 08:56:36AM -0700, pe...@easthope.ca wrote:
> * From: Reco
> > You're breaking threading. Just a friendly note.
>
> I've been adding References manually.
You need to add "In-Reply-To:" as well. And stop doing whatever it is
you&#
* From: Reco
On 19/06/2019 22:22, bw wrote:
> In-Reply-To:
>
Just so you know, this line has to be in the headers for it to work.
You're sending it as the first line of the body (after the blank line
that separates headers from the body). This only pollutes the message,
and still breaks the thread.
--
LILO,
On Sun, 29 Oct 2017, none wrote:
So is there an example ocaml code that can trigger the bug ?
Read the first referece (the INRIA ocaml bug report) throughoutly. It
has been public since day one.
And read all references in the updates I sent to that thread too, for
good measure. It is not
On 10/29/2017 01:17 AM, none wrote:
So is there an example ocaml code that can trigger the bug ?
Debian Linux reveals Intel Skylake and Kaby Lake processors have broken
hyper-threading
http://www.zdnet.com/article/debian-linux-reveals-intel-skylake-kaby-lake-processors-have-broken-hyper
On Sun, 29 Oct 2017, none wrote:
> So is there an example ocaml code that can trigger the bug ?
Read the first referece (the INRIA ocaml bug report) throughoutly. It
has been public since day one.
And read all references in the updates I sent to that thread too, for
good measure. It is not like
So is there an example ocaml code that can trigger the bug ?
Hi.
On Thu, 24 Aug 2017 08:25:16 -0500
David Wright wrote:
> On Thu 24 Aug 2017 at 12:30:35 (+0300), Reco wrote:
> > Hi.
> >
> > In-Reply-To: <20170824074515.y4z2ummdigk2fcbn@kazuki.local>
> >
> [...]
>
> If you type:
>
> :
> set edit_headers
>
> you should get the heade
On Thu 24 Aug 2017 at 12:30:35 (+0300), Reco wrote:
> Hi.
>
> In-Reply-To: <20170824074515.y4z2ummdigk2fcbn@kazuki.local>
>
[...]
If you type:
:
set edit_headers
you should get the headers included in your composition window,
and you can then stick the In-Reply-To: amongst its pe
Hi Henrique,
* Henrique de Moraes Holschuh [2017-07-23 14:56 -0300]:
> TL;DR: Intel has issued public microcode updates in 2017-07-07, fixing
> the hyper-threading errata on every affected processor. These updates
> have been included in the stable and oldstable point releases from
TL;DR: Intel has issued public microcode updates in 2017-07-07, fixing
the hyper-threading errata on every affected processor. These updates
have been included in the stable and oldstable point releases from
2017-07-22.
The microcode updates in the "intel-microcode" packages wit
John Elliot V wrote:
> KDE -> System Settings -> Multimedia (Hardware) -> Audio and Video ->
> Audio Hardware Setup
I was going to say - it is just KDE :D - crap
odels.
>
> Attached, you will find a perl script that can help detect if your
> system is affected or not. Many thanks to Uwe Kleine-König for
> suggesting, and writing this script.
Uwe Kleine-König was kind enough to update the perl script to fix the
broken hyper-threading detectio
odels.
>
> Attached, you will find a perl script that can help detect if your
> system is affected or not. Many thanks to Uwe Kleine-König for
> suggesting, and writing this script.
Uwe Kleine-König was kind enough to update the perl script to fix the
broken hyper-threading detectio
ion of the "7th gen. Core Family specification update" (which is
listed in the references section).
Please note that the "7th gen. Core i7 X-series processors" (Kaby
Lake-X) both support hyper-threading and share the processor signature
(family, model number and stepping) with
On 27/06/17 03:16, John Elliot V wrote:
> Hmm. I re-enabled hyper-threading (to test) and sound didn't come back.
After a number of false starts I was able to restore audio by:
KDE -> System Settings -> Multimedia (Hardware) -> Audio and Video ->
Audio Hardware Setup
HEDT), their related server processors (such as Xeon v5 and Xeon v6), as
well as select Intel Pentium processor models.
TL;DR: unfixed Skylake and Kaby Lake processors could, in some
situations, dangerously misbehave when hyper-threading is enabled.
Disable hyper-threading immediately in BIOS/UEFI to wor
On 27/06/17 02:47, John Elliot V wrote:
> I disabled hyper-threading in my BIOS in response to this advisory (I
> have an i7-7700K). Now I get weird graphical artifacts in drop-down
> lists in KDE (they flash between black and white background) and sound
> has stopped working on my
I disabled hyper-threading in my BIOS in response to this advisory (I
have an i7-7700K). Now I get weird graphical artifacts in drop-down
lists in KDE (they flash between black and white background) and sound
has stopped working on my system. Can anyone guess why that might be
happening? I might
Minor update on the issue:
The check command provided in the advisory to test for hyper-threading
doesn't work: it will always report hyper-theading as enabled. A better
command is provided below.
Note: this also means the perl script will give some false-positives.
I apologise fo
For the record: the email with the perl script doesn't contain malware.
The "malware" alert came from an extremely badly configured system that
violates every best practice in the field: it sends email to every
original recipient (and not just to local users), and it FORGES its
headers to look lik
On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote:
> This warning advisory is relevant for users of systems with the Intel
> processors code-named "Skylake" and "Kaby Lake". These are: the 6th and
> 7th generation Intel Core processors (desktop, embedded, mobile and
> HEDT), their related ser
rocode is new enough\n";
} elsif ($hyperthreading ne "on") {
print "but hyper threading is off, which works around the problem\n";
} else {
print "you should install the latest intel-microcode\n";
}
} else {
print "You may
), as
well as select Intel Pentium processor models.
TL;DR: unfixed Skylake and Kaby Lake processors could, in some
situations, dangerously misbehave when hyper-threading is enabled.
Disable hyper-threading immediately in BIOS/UEFI to work around the
problem. Read this advisory for instruc
Outlook that
> started a new "conversation". Outlook "conversations" grouped by
> subject is a poor substitute for message threading. Are you sure it
> is really threads and not conversations?
Yes, that's exactly what I meant and I prefer real threading anytime.
On 20140804_2358+0300, Andrei POPESCU wrote:
> On Du, 03 aug 14, 13:28:06, Bob Proulx wrote:
> >
> > P.S. I still think digests are less desirable because I don't see a
> > way to view the discussion in a threaded view. Threaded views have
> > been around for so long that I couldn't live without
On 8/5/2014 10:24 PM, Paul E Condon wrote:
> On 20140805_0004+0300, Andrei POPESCU wrote:
>> On Lu, 04 aug 14, 08:52:17, Paul E Condon wrote:
>>>
>>> I've spent some time recently, trying to use the Gmail browser
>>> interface. I would never switch to it from Mutt, excepting only if
>>> Microsoft d
On 20140805_0004+0300, Andrei POPESCU wrote:
> On Lu, 04 aug 14, 08:52:17, Paul E Condon wrote:
> >
> > I've spent some time recently, trying to use the Gmail browser
> > interface. I would never switch to it from Mutt, excepting only if
> > Microsoft does a corporate take-over of Debian (They are
anged the subject then in Outlook that
started a new "conversation". Outlook "conversations" grouped by
subject is a poor substitute for message threading. Are you sure it
is really threads and not conversations?
Gmail also only supports the same group by subject model. Howeve
On Monday 04 August 2014 21:58:36 Andrei POPESCU wrote:
> I'm not very familiar with Gmail's interface
Lucky you. ;-)
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debi
On Lu, 04 aug 14, 08:52:17, Paul E Condon wrote:
>
> I've spent some time recently, trying to use the Gmail browser
> interface. I would never switch to it from Mutt, excepting only if
> Microsoft does a corporate take-over of Debian (They are both
> corporations under the Law, and under the Law,
On Du, 03 aug 14, 13:28:06, Bob Proulx wrote:
>
> P.S. I still think digests are less desirable because I don't see a
> way to view the discussion in a threaded view. Threaded views have
> been around for so long that I couldn't live without them. Of course
> Gmail and Outlook users don't have t
On 20140803_1328-0600, Bob Proulx wrote:
> Bob Proulx wrote:
> > I used a variety of mailers back then and I don't recall which ones
> > handled digests nicely and which did not.
>
> I just tested mutt and digests and mutt handles message digests quite
> well. And furthermore because the Debian l
On Dom, 03 Ago 2014, Bob Proulx wrote:
The inability of people to deal with digest messages these days is the
main reason I think digests should be removed as a mailing list
option.
+1 to that.
I'd also like a filter that rejects mails that have Re: (and
variations) in the Subject and no In-
Bob Proulx wrote:
> I used a variety of mailers back then and I don't recall which ones
> handled digests nicely and which did not.
I just tested mutt and digests and mutt handles message digests quite
well. And furthermore because the Debian lists includes the
individual messages as MIME attemen
eplace with the desired re: Should
> not this be OK.
It is not okay because you have not set In-Reply-To nor References
properly. That breaks threading.
> Or is there some header or marker I should be hitting as well?
The inability of people to deal with digest messages these days is the
main
On Sun, 3 Aug 2014 12:38:16 -0400
AW wrote:
Hello AW,
>lists. So, I don't know what I'm doing with regards to top/bottom
>postings, quoting, etc... There are many good reasons why a particular
Based on that and what you go on to say, it's obvious you're willing to
learn about what is or isn'
On Sun, 3 Aug 2014 16:41:17 +0100
Brad Rogers wrote:
>Quite an achievement, given that
>99.% of MUAs quote correctly "out of the box".
I'm fairly old to Debian. I run a few email servers. I know the ins
and outs of lots of things. And yet, I've rarely posted to mailing
lists. So, I don
On Sun, 3 Aug 2014 10:55:00 -0400
Steve Litt wrote:
Hello Steve,
>Yes, but *not* changing the Subject is an atrocity. I've often thought
>of piping everything with digest type Subjects to /dev/null. Another
>atrocity is these guys who leave the entire digest intact when replying.
I tend to agre
On Wed, 30 Jul 2014 09:42:53 +0100
Brad Rogers wrote:
> On Wed, 30 Jul 2014 10:14:20 +0300
> David Baron wrote:
>
> Hello David,
>
> >Or is there some header or marker I should be hitting as well?
>
> Reference and/or Reply-To headers. The digest, depending on /exactly/
> how it as construct
On Wednesday 30 July 2014 08:14:20 David Baron wrote:
> I do not understand the difference. If I hit reply, so I get the title of
> the digest which I replace with the desired re: Should not this be OK.
No. It gives rise to a new thread, with the digest data, which is not the
same as the he
On Wed, 30 Jul 2014 08:26:04 -0400
The Wanderer wrote:
Hello The,
>(References: and In-Reply-To:, surely?)
You are, of course, right. My brain was waaay ahead of my fingers at
the time. My apologies for any confusion caused.
--
Regards _
/ ) "The blindingly obvious is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/30/2014 04:42 AM, Brad Rogers wrote:
> On Wed, 30 Jul 2014 10:14:20 +0300 David Baron
> wrote:
>
> Hello David,
>
>> Or is there some header or marker I should be hitting as well?
>
> Reference and/or Reply-To headers.
(References: and In
On Wed, 30 Jul 2014 10:14:20 +0300
David Baron wrote:
Hello David,
>Or is there some header or marker I should be hitting as well?
Reference and/or Reply-To headers. The digest, depending on /exactly/
how it as constructed and /exactly/ how you reply, won't necessarily
carry the right headers
On Wednesday 30 July 2014 02:52:38 debian-user-digest-requ...@lists.debian.org
wrote:
> > When you reply threading is broken. Surely you can see that. Could be
> > kmail of course.
>
> Replying from the digest breaks threads. I eschew KDE 4, so I don't know
> abo
On 08/11/12 22:45, Martin Steigerwald wrote:
Am Donnerstag, 8. November 2012 schrieb Philip Ashmore:
So I think there is a bug in cpuid.
Reported as "cupid reports wrong hyper-threading count".
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692799
Regards,
Philip Ashmo
; > Regarding the subject of you mail:
> >
> > Thats in total 8 siblings.
> >
> > So you divide 8 / 4 and get 2 siblings per core. I never seen any
> > hyperthreading with more than 2 siblings per core so far.
> >
> > Ciao,
>
> I guess I wasn&#x
ring: " Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz"
CLFLUSH instruction cache line size: 8
Initial APIC ID: 3
Hyper threading siblings: 16
Feature flags bfebfbff:
FPUFloating Point Unit
VMEVirtual 8086 Mode Enhancements
DE Debugging Extensions
PSEPage Size Extensions
Am Donnerstag, 8. November 2012 schrieb Philip Ashmore:
> But cat /proc/cpuinfo says:
> ...
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 42
> model name : Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz
> stepping: 7
> microcode : 0x2
Am Donnerstag, 8. November 2012 schrieb Philip Ashmore:
> But cat /proc/cpuinfo says:
> ...
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 42
> model name : Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz
> stepping: 7
> microcode : 0x2
But cat /proc/cpuinfo says:
...
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz
stepping: 7
microcode : 0x28
cpu MHz : 2201.000
cache size : 6144 KB
physical id :
From: Camaleon
Date: Thu, 31 May 2012 16:25:20 + (UTC)
> "http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426149";
> Most probably my Pan version (0.132) still has that bug.
http://tools.ietf.org/html/rfc5322#section-3.6 states,
"The only required header fields are the origination date f
On Thu, 31 May 2012 08:40:38 -0800, peter wrote:
> CamaleA3n,
>
> From: Camaleon
> Date: Thu, 31 May 2012 14:11:05 + (UTC)
>> Let's see how this post goes out (I've just tweaked a setting within
>> Pan).
>
> According to the principle "avoid redundant information", leaving your
> mailer con
CamaleA3n,
From: Camaleon
Date: Thu, 31 May 2012 14:11:05 + (UTC)
> Let's see how this post goes out (I've just tweaked a setting within Pan).
According to the principle "avoid redundant information", leaving
your mailer configured to not send In-reply-to is preferable.
Also helpful to
t:
>
> 1. It's not a reply to the old thread. 2. It's not related to the old
> thread in any way. 3. Messes up threading in email clients.
All of these good suggestions are resumed and printed for further
reference in these two links:
http://www.debian.org/Maili
On Monday 28 May 2012 19:21:03 Andrei POPESCU wrote:
> Unfortunately MS Outlook[1]
> threads only by subject, which is very annoying when the subject gets
> even the slightest change.
Gmail too. Which also messes up threading by breaking it when it shouldn't.
Lisi
--
To UNSU
On Lu, 28 mai 12, 18:47:44, rjc wrote:
> 3. Messes up threading in email clients.
... in *inteligent* email clients maybe :) Unfortunately MS Outlook[1]
threads only by subject, which is very annoying when the subject gets
even the slightest change.
[1] having to use it is one of the unpleas
to the old thread in any way.
3. Messes up threading in email clients.
Thank you,
--
rjc
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120528174743.ga3...@linuxstuff.pl
* From: lee
* Date: Mon, 20 Jun 2011 02:59:40 +0200
> [References] go back to beginnings of subthreads at
> least. > With only the In-Reply-To: header, threads would be broken ...
In http://wiki.debian.org/DebianMailingLists I've added a
section "Message Thr
On Sat, Jun 25, 2011 at 03:54:51PM +1000, Andrew McGlashan wrote:
> Test reply from link in archive at:
>
> http://lists.debian.org/debian-user/2011/06/msg01787.html
>
> I want to see if the reply ends up in the thread properly, I think
> it should as the html link from the online archive is th
ink it
>> should as the html link from the online archive is this:
>>
>>
>> > href="mailto:debian-user@lists.debian.org?In-Reply-To=<8db18074-5ae4-4e07-aac5-c41967b5e...@queernet.org>&Subject=Re:%20Re:
>> posting (was: Threading)">debian-use
his:
>
>
> href="mailto:debian-user@lists.debian.org?In-Reply-To=<8db18074-5ae4-4e07-aac5-c41967b5e...@queernet.org>&Subject=Re:%20Re:
> posting (was: Threading)">debian-user@lists.debian.org
>
>
Threads fine in Icedove, Kmail, and on http://lists.deb
074-5ae4-4e07-aac5-c41967b5e...@queernet.org>&Subject=Re:%20Re:
posting (was: Threading)">debian-user@lists.debian.org
--
Kind Regards
AndrewM
Andrew McGlashan
Broadband Solutions now including VoIP
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a
On 25/06/11 02:38, Celejar wrote:
> On Wed, 22 Jun 2011 22:04:24 +1000
> Scott Ferguson wrote:
>
> ...
>
>> If someone feels the need to subscribe to the "digest" version - which
>> is not one "bit" smaller than all the individual messages - it's no
>
> It's not? Aren't many of the many headers
On Wed, 22 Jun 2011 22:04:24 +1000
Scott Ferguson wrote:
...
> If someone feels the need to subscribe to the "digest" version - which
> is not one "bit" smaller than all the individual messages - it's no
It's not? Aren't many of the many headers not repeated per each digest
element?
Celejar
--
On Jun 22, 2011, at 7:01 AM, lee wrote:
> Hm, I wonder why anyone is going to the lengths of replying to digest
> messages rather than just subscribing to the list ...
So they don't need to get hundreds of separate messages?! Most people don't
treat a digest as separate from a list, just an al
Scott Ferguson writes:
> On 22/06/11 21:53, Camaleón wrote:
>>> On 21/06/11 23:29, Camaleón wrote:
On Tue, 21 Jun 2011 09:21:01 -0300, Eduardo M KALINOWSKI wrote:
> But at least you did not reply to a digest.
Sure. I'd say digests are for reading more than replying.
>
> And I
web mail interfaces) that also
do not set threading headers.
--
You will lose an important tape file.
Eduardo M KALINOWSKI
edua...@kalinowski.com.br
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debi
On Ter, 21 Jun 2011, wrote:
So if they preceed the To: field, they are omitted.
This time they are between To: and Subject:.
You'd have to read the RFCs to see if they say anything about that. I
don't recall any requirement of header order (except for Received
headers), but I've never read
On 22/06/11 21:53, Camaleón wrote:
> On Wed, 22 Jun 2011 11:49:05 +1000, Scott Ferguson wrote:
>
>> On 21/06/11 23:29, Camaleón wrote:
>>> On Tue, 21 Jun 2011 09:21:01 -0300, Eduardo M KALINOWSKI wrote:
>
> (...)
>
But at least you did not reply to a digest.
>>>
>>> Sure. I'd say digests
On Wed, 22 Jun 2011 11:49:05 +1000, Scott Ferguson wrote:
> On 21/06/11 23:29, Camaleón wrote:
>> On Tue, 21 Jun 2011 09:21:01 -0300, Eduardo M KALINOWSKI wrote:
(...)
>>> But at least you did not reply to a digest.
>>
>> Sure. I'd say digests are for reading more than replying.
>>
>>
>>
>
ere are some MUAs that can extract individual messages
>> from digests. Emacs gnus does this.
>
> But does it set proper References headers so as not to break
> threading, or does it just strip unnecessary quoted text and sets a
> proper Subject header? (Which are good things, but
On 21/06/11 23:29, Camaleón wrote:
> On Tue, 21 Jun 2011 09:21:01 -0300, Eduardo M KALINOWSKI wrote:
>
>> On Seg, 20 Jun 2011, wrote:
>>> [To see how it works, I've tried to include all the References in the
>>> header in this message. If Chuck or Lee complains I'll know there's an
>>> error. ]
From: Eduardo M KALINOWSKI
Date: Tue, 21 Jun 2011 09:21:01 -0300
> It has not References or In-Reply-To headers.
So if they preceed the To: field, they are omitted.
This time they are between To: and Subject:.
> As someone said, your MUA should do that, not you. If it doesn't,
> consider a
t set proper References headers so as not to break
threading, or does it just strip unnecessary quoted text and sets a
proper Subject header? (Which are good things, but not sufficient.)
--
I've already got a female to worry about. Her name is the Enterprise.
-- Kirk, &quo
Camaleón writes:
>> But at least you did not reply to a digest.
>
> Sure. I'd say digests are for reading more than replying.
In addition, there are some MUAs that can extract individual messages
from digests. Emacs gnus does this.
--
Alberto
--
To UNSUBSCRIBE, email to debian-user-requ...@l
On Tue, 21 Jun 2011 09:21:01 -0300, Eduardo M KALINOWSKI wrote:
> On Seg, 20 Jun 2011, wrote:
>> [To see how it works, I've tried to include all the References in the
>> header in this message. If Chuck or Lee complains I'll know there's an
>> error. ]
>
> This message broke the thread. It has
On Seg, 20 Jun 2011, wrote:
[To see how it works, I've tried to include all the References
in the header in this message. If Chuck or Lee complains I'll
know there's an error. ]
This message broke the thread. It has not References or In-Reply-To headers.
As someone said, your MUA should do t
On Sun, 19 Jun 2011 15:15:57 -0800, peasthope wrote:
>> Would you please fix your mail client so you stop breaking the list
>> threading?
>
> Usually I manage to set In-reply-to to the Message-id of the message
> being replied to. In the Web archive, the Follow-Ups and
yed as the top of a new
>> thread.
>
> Yes, I intended to start a new thread on "message threading". Hence
> the subject "message threading; was Re (3): QCAD Pro in Squeeze".
That´s why I´m asking. I think it´s more common to use a new subject
when starting
new
> thread.
Yes, I intended to start a new thread on "message threading". Hence
the subject "message threading; was Re (3): QCAD Pro in Squeeze".
Thanks, ... Peter E.
--
Telephone 1 360 450 2132. bcc: peasthope at shaw.ca
Shop pages http://car
On 06/19/2011 06:15 PM, peasth...@shaw.ca wrote:
From a private message;
From: C P
Date: Sun, 19 Jun 2011 16:30:55 -0400
Would you please fix your mail client so you stop breaking the list
threading?
Usually I manage to set In-reply-to to the Message-id of the message
being replied to
peasth...@shaw.ca writes:
>>From a private message;
> From: C P
> Date: Sun, 19 Jun 2011 16:30:55 -0400
>> Would you please fix your mail client so you stop breaking the list
>> threading?
>
> Usually I manage to set In-reply-to to the Message-id of the message
&
>From a private message;
From: C P
Date: Sun, 19 Jun 2011 16:30:55 -0400
> Would you please fix your mail client so you stop breaking the list
> threading?
Usually I manage to set In-reply-to to the Message-id of the message
being replied to. In the Web archive, the Follo
From: Bob Proulx
Date: Tue, 18 Jan 2011 21:12:47 -0700
> I am suggesting that you have such a complicated routing setup that it
> is causing you difficulty and that you should simplify it by some
> method. You listed five (5!) route commands in your configuration.
Yes; addressing subnets rat
From: Bob Proulx
Date: Tue, 18 Jan 2011 21:12:47 -0700
> And you have been having such trouble with your vpn(s). To me that is
> like a house of cards. A light breeze blows it over. In order to be
> more robust it needs to be simpler, less rigid, and more flexible.
Iprovements in progress.
On Wednesday 19 January 2011 04:12:47 Bob Proulx wrote:
> peasth...@shaw.ca wrote:
> > Bob Proulx wrote:
> > > You have a complicated setup!
> >
> > A complex setup. "complicated" is a verb. ... Sorry.
>
> Uhm... No. Complicated is an adjective.
>
> From WordNet (r) 2.0 [wn]:
>
>complicate
1 - 100 of 261 matches
Mail list logo
