From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rene Herman Subject: Re: HG branches Date: Wed, 06 Feb 2008 21:06:57 +0100 Message-ID: <47AA1361.7070201@keyaccess.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from smtpq1.tilbu1.nb.home.nl (smtpq1.tilbu1.nb.home.nl [213.51.146.200]) by alsa0.perex.cz (Postfix) with ESMTP id 3ABBB103933 for ; Wed, 6 Feb 2008 21:05:51 +0100 (CET) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Jaroslav Kysela Cc: Takashi Iwai , ALSA development List-Id: alsa-devel@alsa-project.org On 06-02-08 15:06, Jaroslav Kysela wrote: > BTW: Does anyone know if it's possible to just pick a patch from a HG > branch to another? STG (Stacked GIT) has nice 'stg pick @' > command for this. Not me, but thought I'd take the opportunity to ask if switching to git is (still) an absolute no. As far as I can see, hg has mostly downsides, with needing a conduit between it and upstream for example that I saw Linus complain about recently. I'm used to git by now, and every time I try do something inside ALSA I just keep on typing the wrong commands to hg, needing the manpage, not being certain that I'm not fucking up my local tree... I can definitely say that hg is not being instrumental in making me more of a contributor. When I _do_ do something I tend to just work against the kernel inside git and then only in the end apply the result to the current hg just to see if it will. I believe the git submodule stuff would also nicely allow all of ALSA to be one giant repo basically, with kernel, lib, ..., as submodules. Rene.