From: Joe Perches <joe@perches.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Marcin Slusarz <marcin.slusarz@gmail.com>,
Lucas Stach <dev@lynxeye.de>, Borislav Petkov <bp@alien8.de>,
dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
Maarten Lankhorst <maarten.lankhorst@canonical.com>,
linux-tegra@vger.kernel.org, Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH V2 3/3] get_maintainer: prevent keywords from matching filenames
Date: Wed, 06 Mar 2013 22:55:11 -0800 [thread overview]
Message-ID: <1362639311.5290.28.camel@joe-AO722> (raw)
In-Reply-To: <51383800.7000608@wwwdotorg.org>
On Wed, 2013-03-06 at 23:47 -0700, Stephen Warren wrote:
> On 03/06/2013 05:40 PM, Joe Perches wrote:
> > Which is why I showed the whole thing in a single patch.
> > No worries if it's simply to increase the patch count...
>
> I'm not sure what showed refers to?
The changes I posted with the suggestion
https://lkml.org/lkml/2013/3/6/468
> I guess if I squashed /everything/ into a single commit (i.e. the change
> to the Tegra section in MAINTAINERS too) then there wouldn't be any
> bisect issues. I really don't care about patch count. The reason for >1
> patch is that there's often push-back if doing logically separate things
> (adding N: feature, modifying a MAINTAINERS entry to use it, removing
> part of K: feature) in a single patch...
Not from me anyway.
I think it's a single logical change and
it's trivial too.
No worries whatever happens.
prev parent reply other threads:[~2013-03-07 6:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 0:28 [PATCH V2 1/3] get_maintainer: create filename-only regex match type Stephen Warren
2013-03-07 0:29 ` [PATCH V2 2/3] MAINTAINERS: tegra: match related files using N: not K: Stephen Warren
2013-03-07 0:29 ` [PATCH V2 3/3] get_maintainer: prevent keywords from matching filenames Stephen Warren
2013-03-07 0:30 ` Joe Perches
2013-03-07 0:34 ` Stephen Warren
2013-03-07 0:40 ` Joe Perches
2013-03-07 6:47 ` Stephen Warren
2013-03-07 6:55 ` Joe Perches [this message]
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=1362639311.5290.28.camel@joe-AO722 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dev@lynxeye.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maarten.lankhorst@canonical.com \
--cc=marcin.slusarz@gmail.com \
--cc=nouveau@lists.freedesktop.org \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
/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®