From: Joe Perches <joe@perches.com>
To: Marti Raudsepp <marti@juffo.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] scripts/get_maintainer.pl: also find maintainers from Mercurial (hg log)
Date: Mon, 26 Oct 2009 10:27:44 -0700 [thread overview]
Message-ID: <1256578064.1865.96.camel@Joe-Laptop.home> (raw)
In-Reply-To: <1256573044.7754.20.camel@localhost>
On Mon, 2009-10-26 at 18:04 +0200, Marti Raudsepp wrote:
> Hi!
Hi Marti.
> Given that there are official hg repositories available from kernel.org,
> Mercurial seems to be an acceptable alternative to git.
> Does this patch have any chance?
The idea is fine by me.
Here are a couple of things to consider:
There are a few outstanding patches to get_maintainer
so this doesn't apply to latest, but it's not problem
to fix it up.
What about using hg annotate for the git blame?
hg annotate -c $file
and
hg annotate --template="{desc}\n" -r $rev
Is there an hg annotate select line range capability?
I'm not a user of hg. I did:
hg clone http://www.kernel.org/hg/linux-2.6/
and
hg annotate -c -l README
and the output line numbering style isn't clear to me.
Maybe it's better not to introduce more arguments.
Would it be acceptable to use --git instead of --hg
and just execute hg if .git wasn't available but .hg
was? Basically just consider --git the equivalent of
--vcs and execute whatever vcs system was supported?
Or maybe just add --vcs instead of --hg so that
the perforce/cvs/svn/darcs/VisualSourceSafe/etc users
could be happy in the future too...
What do you think?
cheers, Joe
next prev parent reply other threads:[~2009-10-26 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 16:04 Marti Raudsepp
2009-10-26 17:27 ` Joe Perches [this message]
2009-10-26 18:27 ` Marti Raudsepp
2009-10-26 18:53 ` Joe Perches
2009-10-26 19:07 ` Marti Raudsepp
2009-10-29 19:23 ` [PATCH] scripts/get_maintainer.pl: Support multiple VCSs - add mercurial 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=1256578064.1865.96.camel@Joe-Laptop.home \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marti@juffo.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®