[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: dealing with local patches - mercurial queues over bzr/git checkout

From: Daniel Colascione
Subject: Re: dealing with local patches - mercurial queues over bzr/git checkout
Date: Mon, 06 Jan 2014 12:09:51 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0

On 01/06/2014 11:11 AM, Jarek Czekalski wrote:
[this message is sent with 1 day delay - gnu.org seems to ignore my direct
I was thinking of writing about this since long, but now it may be more
important. The discussion concentrates on a change to the version control
system, so that it be better for the devs.

In my approach I don't pay much attention to the version control system used
by a project, because I always init a mercurial repository on top of it.
Then I use mercurial queues concept. This is a very convenient way of
maintaining local patches. The patches are stored as raw patch files and the
mercurial interface provides means of applying, reverting and reordering the

quilt needs that approach, but git's is far cleaner because it's integrated into the VCS. There's no need for a queue setup when git's branches have all the required functionality. Mercurial's artificial distinction between branches and other kinds of change groupings is one of the things I dislike most about the system. I feel strongly that git got it fundamentally right and Mercurial got it fundamentally wrong.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]