From: Joe Perches <joe@perches.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch] get_maintainer: handle file names beginning with ./
Date: Fri, 08 Jan 2016 09:47:07 -0800 [thread overview]
Message-ID: <1452275227.4028.76.camel@perches.com> (raw)
In-Reply-To: <20160108134402.GD5177@mwanda>
On Fri, 2016-01-08 at 16:44 +0300, Dan Carpenter wrote:
> On Fri, Jan 08, 2016 at 03:37:56AM -0800, Joe Perches wrote:
> > On Fri, 2016-01-08 at 13:51 +0300, Dan Carpenter wrote:
> > > The problem is that get_maintainer.pl doesn't work if you have a ./
> > > prefix on the filename. For example, if you type:
> > >
> > > ./scripts/get_maintainer.pl -f ./drivers/usb/usb-skeleton.c
> >
> > Someone's been feeding find output to get_maintainer?
>
> Yep.
So strip the leading './' before using it.
Also, if you're looking for unmaintained files,
I think have a script for that too.
> > Then maybe you'd also have to consider fully qualified
> > file names, tilde expansion, $PWD, and probably a bunch
> > of other things too.
>
> I don't think you'd "have" to consider those as well, but I won't stand
> in your way if you want to...
Half measures aren't generally good enough.
Using a combination of CWnd abs_fast_path and $lk_path
is probably better. $lkpath is set to './' by default.
next prev parent reply other threads:[~2016-01-08 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 10:51 [patch] get_maintainer: handle file names beginning with ./ Dan Carpenter
2016-01-08 11:37 ` Joe Perches
2016-01-08 13:44 ` Dan Carpenter
2016-01-08 17:47 ` Joe Perches [this message]
2016-01-08 18:46 ` Dan Carpenter
2016-01-08 19:46 ` 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=1452275227.4028.76.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.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