Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
	ALSA development <alsa-devel@alsa-project.org>
Subject: Re: HG branches
Date: Wed, 06 Feb 2008 21:06:57 +0100	[thread overview]
Message-ID: <47AA1361.7070201@keyaccess.nl> (raw)
In-Reply-To: <Pine.LNX.4.61.0802061505470.8113@tm8103.perex-int.cz>

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 <branch>@<patch>'
> 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.

  parent reply	other threads:[~2008-02-06 20:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 15:02 HG branches Takashi Iwai
2008-02-06 14:04 ` Jaroslav Kysela
2008-02-06 14:06   ` Jaroslav Kysela
2008-02-06 16:13     ` Takashi Iwai
2008-02-06 20:06     ` Rene Herman [this message]
2008-02-07 11:37       ` Takashi Iwai
2008-02-07 21:10         ` GIT submodules Rene Herman
2008-02-07 21:24         ` Rene Herman
2008-02-07  1:59     ` HG branches Seth Forshee
2008-02-07  8:18       ` Jaroslav Kysela
2008-02-07 11:30       ` Takashi Iwai

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=47AA1361.7070201@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.de \
    /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