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 17:37:30 -0700 [thread overview]
Message-ID: <1344040650.10710.22.camel@joe2Laptop> (raw)
In-Reply-To: <20120803184743.GA4660@jtriplet-mobl1>
On Fri, 2012-08-03 at 11:47 -0700, Josh Triplett wrote:
> On Fri, Aug 03, 2012 at 11:33:21AM -0700, Joe Perches wrote:
> > 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.
>
> Why?
>
> > I have different scripts that I use for git send-email
> > options --to-cmd and --cc-cmd
> [...snip scripts...]
>
> You've submitted enough patches that you've automated as much of the
> process as you can; I don't think that makes the defaults less
> error-prone.
I think the default use of the get_maintainer script is
actually not scripted but interactive, where the user is
just trying to figure out who the maintainer is.
Anyone using get_maintainer in a scripted way should go
through the effort of figuring out in advance who will
be a recipient.
> Given that you've had to explicitly add --no-rolestats to
> your scripts, that seems like evidence in *favor* of making this change.
Probably not.
> As it stands now, the current default of --rolestats makes the obvious
> command line of
> git send-email --to-cmd='scripts/get_maintainer.pl' *.patch
> send broken emails that go to some maintainers but not all. I think it
> makes sense to change the default so that the obvious usage becomes the
> correct one.
There were some discussions awhile back in 2010 about the
preferred defaults.
Perhaps you can read those discussions about why the default
is the way it is.
cheers, Joe
next prev parent reply other threads:[~2012-08-04 0:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 18:27 [PATCH] scripts/get_maintainer.pl: Default to --no-rolestats when output not a terminal Josh Triplett
2012-08-03 18:33 ` Joe Perches
2012-08-03 18:47 ` Josh Triplett
2012-08-04 0:37 ` Joe Perches [this message]
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=1344040650.10710.22.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