From: Joe Perches <joe@perches.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: threaded patch series
Date: Thu, 23 Sep 2010 07:36:53 +0000 [thread overview]
Message-ID: <1285227413.7286.47.camel@Joe-Laptop> (raw)
In-Reply-To: <AANLkTikkJNwF4LS9rx5=bHM2R0Pm751Y1u9V8iAt0w1A@mail.gmail.com>
On Thu, 2010-09-23 at 00:11 -0700, matt mooney wrote:
> What is needed to get a patch series to be threaded?
> In the recent patch series I sent, I used "git
> send-email" in a script that listed the commands with cc's and such.
> What should I have done?
It depends on what version of git you're using.
I think 1.7 changed the defaults.
I use:
$ git format-patch --thread=shallow --cover-letter ...
then
$ git send-email --nothread --no-chain-reply-to --suppress-cc=self ...
I also sometimes use an option to send-email that generates
the cc's using a shell script with scripts/get_maintainer.pl
$ git send-email --nothread --no-chain-reply-to --suppress-cc=self \
--cc-cmd=<file> ...
Where <file> could be:
$ cat scripts/send-email-listed-MAINTAINERS-only
#!/bin/bash
if [[ $(basename $1) =~ ^0000- ]] ; then
./scripts/get_maintainer.pl --nogit $(dirname $1)/*
else
./scripts/get_maintainer.pl --nogit $1
fi
If the cc list is very long, vger might not accept
the cover letter 0000-<foo> email, so adding --nom
like this could be better:
$ cat scripts/send-email-listed-MAINTAINERS-only
#!/bin/bash
if [[ $(basename $1) =~ ^0000- ]] ; then
./scripts/get_maintainer.pl --nogit --nom $(dirname $1)/*
else
./scripts/get_maintainer.pl --nogit $1
fi
next prev parent reply other threads:[~2010-09-23 7:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinsM5jdU194FR8L3hTvBXk0Tr_oV2E5752NOUpq@mail.gmail.com>
2010-09-23 7:11 ` threaded patch series matt mooney
2010-09-23 7:36 ` Joe Perches [this message]
2010-09-23 8:55 ` Julia Lawall
2010-09-23 9:05 ` Joe Perches
2010-09-23 9:09 ` Vasiliy Kulikov
2010-09-23 12:00 ` Vasiliy Kulikov
2010-09-23 14:57 ` Joe Perches
2010-09-23 15:58 ` Julia Lawall
2010-09-23 17:17 ` [RFC PATCH] sit-send-email.pl: Add --to-cmd Joe Perches
2010-09-23 17:29 ` Ævar Arnfjörð Bjarmason
2010-09-23 17:46 ` Joe Perches
2010-09-23 17:50 ` Ævar Arnfjörð Bjarmason
2010-09-23 18:45 ` [PATCH V2] git-send-email.perl: " Joe Perches
2010-09-23 19:57 ` matt mooney
2010-09-23 22:37 ` Junio C Hamano
2010-09-23 23:16 ` Ævar Arnfjörð Bjarmason
2010-09-24 1:18 ` [PATCH V3] " Joe Perches
2010-09-24 15:32 ` Jakub Narebski
2010-09-24 16:06 ` Joe Perches
2010-09-24 16:47 ` Ævar Arnfjörð Bjarmason
2010-09-24 17:03 ` [PATCH V4] " Joe Perches
2010-09-24 1:20 ` [PATCH V2] " Joe Perches
2010-09-23 18:01 ` threaded patch series matt mooney
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=1285227413.7286.47.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=kernel-janitors@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