backing up my repositories, anything special needed?

[Dustin Sallings]

On Aug 10, 2007, at 16:22 , Jens Alfke wrote:

> I still haven't gotten my head around mq. I've read the chapter in  
> the big book, and followed threads here, and it still seems quite  
> complex. I haven't had a chance to try it out, though; that might  
> help me make sense of it.

	It's one of those things that sounds a lot harder than it is.  It's  
basically just orthogonal, mutable changesets.  The mutability is  
exactly what it sounds like you're looking for.  You can keep  
revising a changeset until it's good enough, then transfer control to  
regular mercurial.

	Basically, you do this:

	hg qinit
	hg qnew some-changes-i-want-to-make
	[edit some stuff]
	hg qrefresh # update the patch with the new changes
	[edit some more stuff]
	hg qrefresh # update the patch with still yet newer changes
	hg qdelete -r some-changes-i-want-to-make # Commit

	``qdelete'' is a strange way to spell commit, of course, but it  
*almost* makes sense.

	 If you use the -c option to qinit, you get revision control of the  
queue itself, so you can use ``qcommit'' to save the state of your  
patch queue.

	The patch queue aspect is actually quite nice as well.  You can, for  
example, work on two different layers of your application (something  
low-level and something built on top of that) in the same queue at  
the same time without breaking stuff.  ``qpush'' and ``qpop'' will  
help you move up and down while keeping your changes separate.

	Most of my hg work these days is mq (although I still submit lots of  
small changesets).

-- 
Dustin Sallings