From: Joe Perches <joe@perches.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, mingo@kernel.org,
laijs@cn.fujitsu.com, dipankar@in.ibm.com,
mathieu.desnoyers@efficios.com, niv@us.ibm.com,
tglx@linutronix.de, peterz@infradead.org, rostedt@goodmis.org,
dhowells@redhat.com, edumazet@google.com, dvhart@linux.intel.com,
fweisbec@gmail.com, oleg@redhat.com, sbw@mit.edu
Subject: Re: [PATCH RFC 2/2] rcu: Add Josh Triplett as designated reviewer
Date: Mon, 02 Jun 2014 20:11:36 -0700 [thread overview]
Message-ID: <1401765096.7323.61.camel@joe-AO725> (raw)
In-Reply-To: <20140603015133.GA20354@thin>
[-- Attachment #1: Type: text/plain, Size: 2165 bytes --]
On Mon, 2014-06-02 at 18:51 -0700, Josh Triplett wrote:
> git send-email can invoke 'scripts/get_maintainer.pl --no-rolestats'
> directly via --to-cmd or -cc-cmd; that works fine as long as you don't
> have a cover letter.
>
> Depending on the system I'm running on, and whether it's more convenient
> to invoke git-send-email or to edit patch mails and send them with 'mutt
> -H', I have a shell pipeline which invokes get_maintainer.pl on an
> entire patch series, collects all the email addresses it returns, and
> inserts them all into each mail as CCs. (That way, when I send a
> cross-subsystem patch series, I don't get a pile of maintainers confused
> that they only received a couple of the numbered patches.) One example:
I think that as long as the appropriate mailing lists receive
the cover letter, any real maintainer won't be confused.
> { echo -n "To: " ; for x in *.patch ; do scripts/get_maintainer.pl --no-rolestats < $x | fgrep -v josh@joshtriplett.org ; done | sort -u | sed 's/$/, /;$s/, $//' | tr -d '\n' ; echo ; } | sed -i '/^From:/r/dev/stdin'
>
> Personally, I'd find it handy if one of the following happened:
>
> - git send-email (and ideally also git format-patch) grew an option to
> collect *all* the to-cmd and cc-cmd output from each patch and apply
> it to every patch (including the cover letter).
The biggest issue with doing that is the
quantity of names and addresses on the [0/n]
patch can easily exceed vger's 1024 byte
maximum header size limit.
I drop all but the primary maintainers and
just cc lists.
I use a couple of scripts for that (attached)
for the "--to_cmd" and "--cc_cmd" options
Another possibility is to add a new "--bcc_cmd"
to git send-email so that vger's header limit
can be worked around.
I had patches to git to do that awhile ago.
> - get_maintainer.pl accepted multiple patchfile names and output the
> union of the results. Ideally, get_maintainer.pl would also have a -i
> option to edit the patch files and insert the addresses in the mail
> headers.
Why would get_maintainer.pl have any option like that?
Tools for uses. Scripting.
Aren't we good at that sort of thing?
[-- Attachment #2: to.sh --]
[-- Type: application/x-shellscript, Size: 345 bytes --]
[-- Attachment #3: cc.sh --]
[-- Type: application/x-shellscript, Size: 211 bytes --]
next prev parent reply other threads:[~2014-06-03 3:11 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 17:00 [PATCH RFC 1/2] MAINTAINERS: Add "R:" designated-reviewers tag Paul E. McKenney
2014-06-02 17:00 ` [PATCH RFC 2/2] rcu: Add Josh Triplett as designated reviewer Paul E. McKenney
2014-06-02 20:35 ` Andrew Morton
2014-06-02 20:36 ` Joe Perches
2014-06-02 20:38 ` Randy Dunlap
2014-06-03 0:02 ` josh
2014-06-03 1:07 ` Randy Dunlap
2014-06-03 1:51 ` Josh Triplett
2014-06-03 3:11 ` Joe Perches [this message]
2014-06-03 5:10 ` Josh Triplett
2014-06-03 5:21 ` Joe Perches
2014-06-03 17:21 ` Randy Dunlap
2014-06-02 17:22 ` [PATCH RFC 1/2] MAINTAINERS: Add "R:" designated-reviewers tag Joe Perches
2014-06-02 17:29 ` Steven Rostedt
2014-06-02 17:34 ` Joe Perches
2014-06-02 17:48 ` josh
2014-06-02 17:59 ` Joe Perches
2014-06-02 18:12 ` Josh Boyer
2014-06-02 18:15 ` Joe Perches
2014-06-02 18:16 ` Paul E. McKenney
2014-06-02 18:44 ` Joe Perches
2014-06-02 18:50 ` Steven Rostedt
2014-06-02 18:55 ` josh
2014-06-02 19:05 ` Joe Perches
2014-06-02 19:09 ` josh
2014-06-02 19:17 ` Joe Perches
2014-06-02 23:19 ` Dave Chinner
2014-06-02 23:24 ` Andrew Morton
2014-06-03 0:35 ` Steven Rostedt
2014-06-02 23:59 ` josh
2014-06-03 0:12 ` Joe Perches
2014-06-03 23:48 ` Ken Moffat
2014-06-04 0:03 ` Steven Rostedt
2014-06-04 0:33 ` Joe Perches
2014-06-03 1:11 ` Dave Chinner
2014-06-03 1:30 ` Steven Rostedt
2014-06-03 7:16 ` Dave Chinner
2014-06-03 13:24 ` Mathieu Desnoyers
2014-06-03 15:54 ` Paul E. McKenney
2014-06-03 17:43 ` Steven Rostedt
2014-06-03 18:05 ` Randy Dunlap
2014-06-03 20:52 ` Theodore Ts'o
2014-06-03 21:46 ` Steven Rostedt
2014-06-03 22:08 ` josh
2014-06-05 4:01 ` Dave Chinner
2014-06-05 21:14 ` Frank Rowand
2014-06-02 19:26 ` Paul E. McKenney
2014-06-02 20:41 ` Dipankar Sarma
2014-06-02 19:07 ` Paul E. McKenney
2014-06-02 18:56 ` josh
2014-06-02 19:08 ` Paul E. McKenney
2014-06-02 19:11 ` josh
2014-06-02 19:27 ` Paul E. McKenney
2014-06-02 19:36 ` Joe Perches
2014-06-02 19:40 ` Randy Dunlap
2014-06-02 20:29 ` josh
2014-06-02 19:50 ` Paul E. McKenney
2014-06-02 19:55 ` Joe Perches
2014-06-02 20:07 ` Paul E. McKenney
2014-06-02 20:25 ` Mathieu Desnoyers
2014-06-03 15:37 ` Paul E. McKenney
2014-06-03 16:16 ` Steven Rostedt
2014-06-03 16:25 ` Paul E. McKenney
2014-06-04 1:35 ` Lai Jiangshan
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=1401765096.7323.61.camel@joe-AO725 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=niv@us.ibm.com \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sbw@mit.edu \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®