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

[Jarek Czekalski]

[this message is sent with 1 day delay - gnu.org seems to ignore my direct
emails]
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
patches.

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).

Jarek

[1]
http://sourceforge.net/apps/mediawiki/jedit/index.php?title=Use_mercurial_queues_over_svn_checkout




--
View this message in context: 
http://emacs.1067599.n5.nabble.com/dealing-with-local-patches-mercurial-queues-over-bzr-git-checkout-tp308685.html
Sent from the Emacs - Dev mailing list archive at Nabble.com.