From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
"containers@lists.linux-foundation.org"
<containers@lists.linux-foundation.org>
Subject: Re: [GIT PULL] binfmt_misc updates for 4.7+ merge window
Date: Wed, 27 Jul 2016 20:58:48 -0700 [thread overview]
Message-ID: <1469678328.3998.33.camel@perches.com> (raw)
In-Reply-To: <CA+55aFwUDnS9POpBJysZurSBsWeyYbMF4qPKjD1sFygeFi7tTg@mail.gmail.com>
On Wed, 2016-07-27 at 20:33 -0700, Linus Torvalds wrote:
> On Wed, Jul 27, 2016 at 8:31 PM, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> > I'd actually prefer to make "--git" the default, if you are inside a
> > git repository. Because obviously the *actual* default is too hard to
> > understand ;)
Well, you are in the minority there.
Most people seem not to want to be cc'd on stuff they may have
sent an odd patch on but don't actually maintain.
You could create a .get_maintainer.conf file and add --git
to it if you want that.
> I'd also like to make the "-f" optional.
>
> I constantly forget it, and curse it. It should be trivial to see "the
> argument is a file that is tracked in git, so it clearly isn't the
> name of a patch".
You could send a patch ;)
I'll look at it in any case.
next prev parent reply other threads:[~2016-07-28 3:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 2:31 [GIT PULL] binfmt_misc updates for 4.7+ merge window James Bottomley
2016-07-28 2:57 ` Joe Perches
2016-07-28 3:12 ` Linus Torvalds
2016-07-28 3:21 ` Joe Perches
2016-07-28 3:26 ` Linus Torvalds
2016-07-28 3:30 ` Joe Perches
2016-07-28 11:07 ` James Bottomley
2016-07-28 3:31 ` Linus Torvalds
2016-07-28 3:33 ` Linus Torvalds
2016-07-28 3:58 ` Joe Perches [this message]
2016-07-28 3:26 ` Joe Perches
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=1469678328.3998.33.camel@perches.com \
--to=joe@perches.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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