public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Joe Perches <joe@perches.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, 8 Jan 2016 21:46:04 +0300	[thread overview]
Message-ID: <20160108184604.GE5177@mwanda> (raw)
In-Reply-To: <1452275227.4028.76.camel@perches.com>

On Fri, Jan 08, 2016 at 09:47:07AM -0800, Joe Perches wrote:
> > > 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.
> 

Those are fake issues though and I can't imagine how they would affect
anyone.  My issue was super annoying for me because I was sending find
output to a script and it was almost mailing the correct people because
it was using git output.  I had to debug for a long time before I
spotted the difference between ./drivers/media/radio/wl128x/fmdrv_common.c
and drivers/media/radio/wl128x/fmdrv_common.c.

I feel like I have seen this before and just manually added the correct
mailing lists back.  It's crazy annoying and easy to do.

> Using a combination of CWnd abs_fast_path and $lk_path
> is probably better.  $lkpath is set to './' by default.

I have no idea what this means...  It sounds like a good idea though.
:)  Please give me Reported-by credit.

regards,
dan carpenter

  reply	other threads:[~2016-01-08 18:46 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
2016-01-08 18:46       ` Dan Carpenter [this message]
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=20160108184604.GE5177@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=joe@perches.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