From: Jens Lautenbacher <jens@lemcbed.lem.uni-karlsruhe.de>
Cc: Steinar Bang <sb@metis.no>
Subject: Re: Puzzle: Why do some follow-ups thread and some not
Date: Fri, 14 Jun 1996 19:34:56 +0200 [thread overview]
Message-ID: <9606141734.AA11833@lemcbed.lem.uni-karlsruhe.de> (raw)
In-Reply-To: <whvigu2vut.fsf@brage.metis.no>
From: Jens Lautenbacher <jens@lemcbed.lem.uni-karlsruhe.de>
Date: 14 Jun 1996 19:34:56 +0200
In-Reply-To: Steinar Bang's message of 14 Jun 1996 18:28:42 +0200
Message-ID: <x2lohqb873.fsf@lemcbed.lem.uni-karlsruhe.de>
Lines: 8
X-Mailer: Gnus v5.2.17/XEmacs 19.14
In your case the answer is quite easy: The second subject line has a
space at the end, the first one not.
I see this happening many times, maybe we could ignore whitespace at
the end of subject lines? (Lars?)
next prev parent reply other threads:[~1996-06-14 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-14 16:28 Steinar Bang
1996-06-14 17:34 ` Jens Lautenbacher [this message]
1996-06-14 22:21 ` Sten Drescher
1996-06-14 22:55 ` Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9606141734.AA11833@lemcbed.lem.uni-karlsruhe.de \
--to=jens@lemcbed.lem.uni-karlsruhe.de \
--cc=sb@metis.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).