[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100512063042.GB5718@cr0.nay.redhat.com>
Date: Wed, 12 May 2010 14:30:42 +0800
From: Américo Wang <xiyou.wangcong@...il.com>
To: Joe Perches <joe@...ches.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Florian Mickler <florian@...kler.org>,
Stephen Hemminger <shemminger@...tta.com>,
Stefan Richter <stefanr@...6.in-berlin.de>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] scripts/get_maintainer.pl: add
.get_maintainer.conf default options file
On Sun, May 09, 2010 at 09:56:03PM -0700, Joe Perches wrote:
>Allow the use of a .get_maintainer.conf file to control the
>default options applied when scripts/get_maintainer.pl is run.
>
>.get_maintainer.conf can contain any valid command-line argument.
>
>File contents are prepended to any additional command line arguments.
>
>Multiple lines may be used, blank lines ignored, # is a comment.
Do we really have to do this? This looks odd to me.
If the user of get_maintainer.pl uses some long command line
arguments, to save his input, he should use bash aliases, not
configure files. I never see configure files used like this.
Also, it doesn't worthy a configure file for such a script like
get_maintainer.pl.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists