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:30:32 -0700 [thread overview]
Message-ID: <1469676632.3998.27.camel@perches.com> (raw)
In-Reply-To: <CA+55aFz3+37s7eQ55kGbEEoGhMtvkAwYQ3szOSVrg3MKA+iWrg@mail.gmail.com>
On Wed, 2016-07-27 at 20:26 -0700, Linus Torvalds wrote:
> On Wed, Jul 27, 2016 at 8:21 PM, Joe Perches <joe@perches.com> wrote:
> >
> > On Wed, 2016-07-27 at 20:12 -0700, Linus Torvalds wrote:
> > >
> > > Did you actually try it.
> > yes.
> Well, in that case the script is buggy. It self-documents as having
> "--git-fallback" on by default, and I'm not seeing anybody claiming
> explicit maintenance of fs/binfmt_misc.c.
>
> Al's match comes from a wildcard, not an exact one.
Nope, the script doesn't have a defect here.
It's documented what the script does with wildcards.
You _could_ argue that the file pattern specified
for VFS is inappropriate though,
next prev parent reply other threads:[~2016-07-28 3:30 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 [this message]
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
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=1469676632.3998.27.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