DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=poSyNO2ee1oEzpdzDJzu1mQexXabp89UCpsJYkQaVQ0tddtEumW6FIrxmSRua6PABJ
         Id2b++N2Jw/nzcSpmOpFDDVPWxLlDW2C2kDlE8cI+VE3eLpwCZCwirL7XvlIOKtkJlc6
         ZWjEQi4mslOri6IF+e8JtGqQvZLIFhSI1rdgY=
Message-ID: <5d5443650812012228u5aad36a2jc3e9e68cd61c27e3@mail.gmail.com>
Date: Tue, 2 Dec 2008 11:58:31 +0530
From: "Trilok Soni" <soni.trilok@gmail.com>
To: "Mauro Carvalho Chehab" <mchehab@infradead.org>
Subject: Re: [PULL] http://www.linuxtv.org/hg/~hverkuil/v4l-dvb
Cc: "Hans Verkuil" <hverkuil@xs4all.nl>,
       "v4l-dvb maintainer list" <v4l-dvb-maintainer@linuxtv.org>,
       v4l <video4linux-list@redhat.com>,
       "Sakari Ailus" <sakari.ailus@nokia.com>,
       "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
       linux-kernel@vger.kernel.org
In-Reply-To: <20081201202209.5cea1f4b@pedra.chehab.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <200812011451.06156.hverkuil@xs4all.nl>
	 <5d5443650812011014q55a96540gc8a4b97be951f2fd@mail.gmail.com>
	 <20081201202209.5cea1f4b@pedra.chehab.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1314
Lines: 31

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.

-- 
---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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/