From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Why are my posts being put in new threads?
Date: Wed, 21 Dec 2011 10:46:35 -0500 [thread overview]
Message-ID: <201112211046.36439.luke@dashjr.org> (raw)
In-Reply-To: <CABr1YTf_s06Z4QgWLOSwjznLPrbGGVRk0=DxKTcGs6t6MZcMFw@mail.gmail.com>
On Wednesday, December 21, 2011 6:50:47 AM Eric Lombrozo wrote:
> I've made a couple recent posts that were intended for the Protocol
> extensions thread but have been put in new threads. What part of the
> email message is used to identify the thread to which it belongs? I
> would have thought the subject, but apparently it isn't.
http://cr.yp.to/immhf/thread.html
prev parent reply other threads:[~2011-12-21 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 11:50 [Bitcoin-development] Why are my posts being put in new threads? Eric Lombrozo
2011-12-21 15:46 ` Luke-Jr [this message]
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=201112211046.36439.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
/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