From: Jonathan Larmour <jifl@jifvik.org>
To: Sergei Gavrikov <sergei.gavrikov@gmail.com>
Cc: Alex Schuilenburg <alexs@ecoscentric.com>,
ecos-maintainers@ecos.sourceware.org
Subject: Re: Bugzilla 3.4.6 and Mercurial 1.5 updates
Date: Sat, 13 Mar 2010 00:20:00 -0000 [thread overview]
Message-ID: <4B9ADA2A.5050702@jifvik.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1003111854400.2083@sg-laptop>
On 11/03/10 19:27, Sergei Gavrikov wrote:
> Of course, practice to clone is useful in some cases, but, I listen how
> Git geeks will say: Git's branching are no-disk-waste operations, and HG
> clones? Hm... Fortunately, I knew the very effective HG's no-disk-waste
> operation, those are `hg q*'.
As I've noted in the large email I've just sent about DCVS's :-), hg has
many more ways to branch than that. Plus hg clones on the same local disk
can use hard links to save space.
> Have a single central repository under HG, setup the DRCSed "repository"
> for a queue of the patches: `hg qinit' and then manage MQs (=patches)
> `hg qnew': do hundreds of HG `hg qrefresh', `hg qcommit' (that is your
> pain, your mistakes, your experimental stuff, if you want nobody see
> that ever) and then in one day type `hg qfinish' to apply excellent
> patch to the central repository.
I know that Nick and Bart who've been using mercurial have been using
these. I've yet to try and use them in anger - my playing so far didn't
get as far as that. They do sound good (like git's staging area).
Jifl
prev parent reply other threads:[~2010-03-13 0:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 10:22 Alex Schuilenburg
2010-03-11 19:27 ` Sergei Gavrikov
2010-03-13 0:20 ` Jonathan Larmour [this message]
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=4B9ADA2A.5050702@jifvik.org \
--to=jifl@jifvik.org \
--cc=alexs@ecoscentric.com \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=sergei.gavrikov@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).