From: John Levon <levon@movementarian.org>
To: jw schultz <jw@pegasys.ws>, linux-kernel@vger.kernel.org
Subject: Re: DVB updates, 3rd try
Date: Thu, 19 Jun 2003 03:13:19 +0100 [thread overview]
Message-ID: <20030619021318.GA53393@compsoc.man.ac.uk> (raw)
In-Reply-To: <20030619014509.GC20116@pegasys.ws>
On Wed, Jun 18, 2003 at 06:45:09PM -0700, jw schultz wrote:
> [over-quoting snipped]
> Please don't do this. $reply_to ||= $message_id is OK but
> having each patch as a reply to the previous one is
> annoying. I think it was Greg who recently posted one set
> of patches that was so large the indentation for the thread
> went off the screen.
>
> [PATCH 0/n] frob the niggle
> |-> [PATCH 1/n] frob the niggle
> |-> [PATCH 2/n] frob the niggle
> |-> [PATCH 3/n] frob the niggle
Then the patches don't appear in order in people's mail readers.
john
next prev parent reply other threads:[~2003-06-19 1:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 13:08 DVB updates, 2nd try Michael Hunold
2003-05-28 10:12 ` Christoph Hellwig
2003-05-28 12:54 ` Michael Hunold
2003-05-28 12:58 ` Christoph Hellwig
2003-06-18 11:49 ` DVB updates, 3rd try Michael Hunold
2003-06-18 15:58 ` Linus Torvalds
2003-06-18 16:12 ` John Levon
2003-06-19 1:45 ` jw schultz
2003-06-19 2:13 ` John Levon [this message]
2003-06-19 8:55 ` jw schultz
2003-06-18 19:39 ` Johannes Stezenbach
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=20030619021318.GA53393@compsoc.man.ac.uk \
--to=levon@movementarian.org \
--cc=jw@pegasys.ws \
--cc=linux-kernel@vger.kernel.org \
/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).