backing up my repositories, anything special needed?

[Dustin Sallings]

On Aug 10, 2007, at 15:33 , Jens Alfke wrote:

> I agree in general, but that doesn't back up local modifications  
> that haven't been checked into the repository yet.
>
> I suppose a rejoinder to that is "check your changes in very  
> often", but I prefer not to check things in until I hit some  
> coherent milestone. Like, the project at least compiles and runs.  
> And sometimes during big refactoring tasks I have spent days in a  
> broken state...
>
> OTOH, backing up just the "M" files would be a pretty easy task to  
> do with a script, not subject to the race conditions of checking in  
> the whole repository.

	You're getting into even more dangerous territory there.  I'm  
definitely one to tell people to check in as early as possible.  I'll  
check in broken code if the alternative is possibly losing the work  
in progress (someone else can always work from an earlier version if  
there's more than one user working on stuff).

	Your development style seems very aligned with mq, though.  I'll add  
complete garbage to mq, and do so often.  mq itself can be revision  
controlled, and *that* can be backed up using regular hg tools.

-- 
Dustin Sallings


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20070810/8c4a37b2/attachment.htm