linux-kernel - Re: [PULL] http://www.linuxtv.org/hg/~hverkuil/v4l-dvb

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 2 Dec 2008 13:30:13 +0530
From:	"Trilok Soni" <soni.trilok@...il.com>
To:	"Mauro Carvalho Chehab" <mchehab@...radead.org>
Cc:	"Hans Verkuil" <hverkuil@...all.nl>,
	"v4l-dvb maintainer list" <v4l-dvb-maintainer@...uxtv.org>,
	v4l <video4linux-list@...hat.com>,
	"Sakari Ailus" <sakari.ailus@...ia.com>,
	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PULL] http://www.linuxtv.org/hg/~hverkuil/v4l-dvb

Hi,

On Tue, Dec 2, 2008 at 11:58 AM, Trilok Soni <soni.trilok@...il.com> wrote:
> Hi Mauro,
>
>>
>> This is one of the lack of the features on mercurial. It doesn't have a meta
>> tag for committer. On mercurial, the -hg user and the author should be the same
>> person.
>>
>> Since we want to identify the patch origin (e.g. whose v4l/dvb maintainer got
>> the patch), we use the internal "user" meta-tag as the committer, and an extra
>> tag, at the patch description for the author (From:).
>>
>> When creating the -git patch, the "From:" tag is replaced, by script, for
>> "Author:", I add my SOB there, and, I add myself as the -git committer (on git
>> we have both meta-tags).
>
> Isn't it good time to move v4l2-dvb tree to GIT? I am not aware of any
> hg-to-git repo. converter, but I can check with hg and git community.
> It could be difficult at first, but I am very confident that there are
> many GIT users here than mercurial, and yes your v4l-dvb maintenance
> process might change due move from GIT, but atleast you will not have
> to internal user meta-data per patch.

OK, there are tools to convert mercurial to git repo.

http://git.or.cz/gitwiki/InterfacesFrontendsAndTools#head-8870e1c81cc93f9a7a7acb5e969924ee60182d6b
http://hedonismbot.wordpress.com/2008/10/16/hg-fast-export-convert-mercurial-repositories-to-git-repositories/


-- 
---Trilok Soni
http://triloksoni.wordpress.com
http://www.linkedin.com/in/triloksoni
--
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/