From: Tim Chase <git@tim.thechases.com>
To: <git@vger.kernel.org>
Subject: Re: coming from git, understanding mercurial branching
Date: Fri, 6 Sep 2013 14:29:27 -0500 [thread overview]
Message-ID: <20130906142927.279a994a@bigbox.christie.dr> (raw)
In-Reply-To: <20130906175124.7d08947410503681449642ad@domain007.com>
On 2013-09-06 17:51, Konstantin Khomoutov wrote:
> I found this guide [1] very useful back in the time I tried to grok
> Mercurial.
>
> 1.
> http://stevelosh.com/blog/2009/08/a-guide-to-branching-in-mercurial/
Indeed, after reading it, that's the most sense I've been able to make
of Mercurial's strange branching. I guess it boils down to the
following rough heuristic:
- if you want to dink around locally, but don't want to publish your
branches (yet), default to bookmarks using "hg bookmark"
- once you want a branch to be public, consider making a "real"
branch using "hg branch"
- if you want complete isolation in case you screw up something like
merging, use a clone
I still prefer Git's way, but at least I'm not left scratching my
head when I have to play with Mercurial branches.
Thanks, all.
-tkc
next prev parent reply other threads:[~2013-09-06 19:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 2:27 coming from git, understanding mercurial branching Tim Chase
2013-09-06 4:39 ` Tay Ray Chuan
2013-09-06 13:26 ` Tim Chase
2013-09-06 13:51 ` Konstantin Khomoutov
2013-09-06 16:40 ` Philip Oakley
2013-09-06 19:29 ` Tim Chase [this message]
2013-09-08 0:42 ` Felipe Contreras
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=20130906142927.279a994a@bigbox.christie.dr \
--to=git@tim.thechases.com \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).