All of lore.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@gmail.com>
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, 6 Feb 2008 19:59:24 -0600	[thread overview]
Message-ID: <20080207015923.GA14226@ubuntu-workstation> (raw)
In-Reply-To: <Pine.LNX.4.61.0802061505470.8113@tm8103.perex-int.cz>

On Wed, Feb 06, 2008 at 03:06:44PM +0100, 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.

  hg update -C dest-branch
  hg transplant -b source-branch revision

But I must say that using branches in hg is rather painful.  We tried
it for a while at my workplace and switched to using cloned repos for
branches (mostly).  We had several instances of bad things happening
because of the way hg handled branches, and when those things got
pushed it was often very difficult to get the repo back to a decent
state.  In my opinion git handles branches much better than hg does.

Cheers,
Seth

  parent reply	other threads:[~2008-02-07  2:00 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
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     ` Seth Forshee [this message]
2008-02-07  8:18       ` HG branches 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=20080207015923.GA14226@ubuntu-workstation \
    --to=seth.forshee@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.