lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 26 Oct 2009 10:27:44 -0700
From:	Joe Perches <>
To:	Marti Raudsepp <>
Cc:	Andrew Morton <>,
Subject: Re: [RFC] scripts/ also find maintainers from
 Mercurial (hg log)

On Mon, 2009-10-26 at 18:04 +0200, Marti Raudsepp wrote:
> Hi!

Hi Marti.

> Given that there are official hg repositories available from,
> 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
	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
	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

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists