[Top][All Lists]

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

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

From: Jarek Czekalski
Subject: dealing with local patches - mercurial queues over bzr/git checkout
Date: Mon, 6 Jan 2014 11:11:34 -0800 (PST)

[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

Don't you think that having a good machinery to deal with local patches
makes it less important what version control is in use? After all you use
only basic commands, like pull, push, log, commit which are so similar
between implementations. And in Emacs we have only 1-2 branches active, with
most people using but the trunk.

The concept is described in a wiki article, Use mercurial queues over svn
checkout [1]. Although I say "my approach" I was actually adviced so by
Stefan Sperling on svn mailing list (the link is inside the article).



View this message in context: 
Sent from the Emacs - Dev mailing list archive at Nabble.com.

reply via email to

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