From: Joe Perches <joe@perches.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Alex Kelly <alex.page.kelly@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Richard Weinberger <richard@nod.at>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts/get_maintainer.pl: Default to --no-rolestats when output not a terminal
Date: Fri, 03 Aug 2012 11:33:21 -0700 [thread overview]
Message-ID: <1344018801.10710.17.camel@joe2Laptop> (raw)
In-Reply-To: <20120803182706.GA4637@jtriplet-mobl1>
On Fri, 2012-08-03 at 11:27 -0700, Josh Triplett wrote:
> scripts/get_maintainer.pl defaults to showing --rolestats, which
> provides annotations explaining why each person or list might want to
> know about a patch. This works well for interactive use, but breaks
> when used with git send-email's --to-cmd or --cc-cmd, resulting in
> malformed email headers and mails sent to some but not all recipients.
>
> To avoid the need to explicitly pass --no-rolestats for batch use,
> enable --rolestats by default only when outputting to a terminal.
Hi Josh.
I think it's preferable to add --no-rolestats
to the uses that need them.
I have different scripts that I use for git send-email
options --to-cmd and --cc-cmd
$ cat ~/bin/to.sh
#!/bin/bash
opts="--nogit --nogit-fallback --norolestats --pattern-depth=1"
if [[ $(basename $1) =~ ^0000- ]] ; then
./scripts/get_maintainer.pl --nom $opts $(dirname $1)/*
else
maint=$(./scripts/get_maintainer.pl --nol $opts $1)
if [ "$maint" == "" ] ; then
echo "linux-kernel@vger.kernel.org"
else
echo "$maint"
fi
fi
$ cat ~/bin/cc.sh
#!/bin/bash
opts="--nogit --nogit-fallback --norolestats"
if [[ $(basename $1) =~ ^0000- ]] ; then
./scripts/get_maintainer.pl --nom $opts $(dirname $1)/*
else
./scripts/get_maintainer.pl $opts $1
fi
next prev parent reply other threads:[~2012-08-03 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 18:27 Josh Triplett
2012-08-03 18:33 ` Joe Perches [this message]
2012-08-03 18:47 ` Josh Triplett
2012-08-04 0:37 ` Joe Perches
2012-08-04 3:57 ` Josh Triplett
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=1344018801.10710.17.camel@joe2Laptop \
--to=joe@perches.com \
--cc=Ian.Campbell@citrix.com \
--cc=akpm@linux-foundation.org \
--cc=alex.page.kelly@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
/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®