From: Sten Drescher <sten.drescher@tivoli.com>
Subject: Re: Puzzle: Why do some follow-ups thread and some not
Date: 14 Jun 1996 17:21:08 -0500 [thread overview]
Message-ID: <vppw72m3hn.fsf@dogbert.tivoli.com> (raw)
In-Reply-To: Jens Lautenbacher's message of Fri, 14 Jun 1996 19:34:56 +0200
>>>>> Jens Lautenbacher writes:
JL> In your case the answer is quite easy: The second subject line has
JL> a space at the end, the first one not.
JL> I see this happening many times, maybe we could ignore whitespace
JL> at the end of subject lines? (Lars?)
And at the beginning - I'm on a mailing list that insists on
using Header:<tab> instead of Header:<space>.
--
+---------------------- Tivoli Customer Support ----------------------+
| Sten Drescher Tivoli Systems, Inc |
| email: sten.drescher@tivoli.com 9442 Capital of Texas Hwy North |
| phone: (512) 794-9070 Arboretum Plaza One, Suite 500 |
| fax : (512) 345-2784 Austin, Texas 78759 |
+-----------------------------------------------------------------------+
next prev parent reply other threads:[~1996-06-14 22:21 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
1996-06-14 22:21 ` Sten Drescher [this message]
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=vppw72m3hn.fsf@dogbert.tivoli.com \
--to=sten.drescher@tivoli.com \
/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).