From: "Jeff Anderson-Lee" <jonah@eecs.berkeley.edu>
To: <linux-kernel@vger.kernel.org>
Subject: [RFC] suggestion [PATCH N/M] subject lines
Date: Tue, 20 Jun 2006 15:50:48 -0700 [thread overview]
Message-ID: <000001c694bb$f9fa3f40$ce2a2080@eecs.berkeley.edu> (raw)
Reading the mailing list with a non-threads compatible
mail client agent would be made much easier if the
convention for subject lines for multi-part patches was
changed to the following:
patch set name [PATCH N/M] patch summary
Then sorting by subject would group all patches for the
Same patch set together.
I don't know if these Subject lines are hand generated, or if there
is software involved that would have to me modified for generating
and/or parsing them.
Comments?
Jeff Anderson-Lee
next reply other threads:[~2006-06-20 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 22:50 Jeff Anderson-Lee [this message]
2006-06-21 9:55 ` Stefan Richter
2006-06-21 10:42 ` Antonio Vargas
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='000001c694bb$f9fa3f40$ce2a2080@eecs.berkeley.edu' \
--to=jonah@eecs.berkeley.edu \
--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
Powered by JetHome