howto suspend work

Masklinn masklinn at masklinn.net
Wed Jun 3 09:07:05 CDT 2009


On 3 Jun 2009, at 15:38 , Neal Becker wrote:
> I have reached a milestone, let's call it revA.  I started working  
> on some
> substantial change, but then realized this is not the right  
> approach.  I
> could just hg revert (I haven't yet committed these new changes),  
> but I'd
> like to keep it just in case.
>
> I could hg ci the new changes, and then hg update -r revA.  That's  
> fine,
> except the head would still be the aborted experiment.
>
> Suggestions?

Possible tools include:

* hg shelve, initial purpose is to temporarily set aside changes  
(usually to rework on them later), if you don't want to shelve other  
things you can use that as a long-term storage for a single patch

* mercurial queues (mq), create a stack of patches, often used to keep  
patches on top of a remote source

* mike mentioned hg tasks

* bookmarks (local branches), just commit your incomplete changes to a  
bookmark, switch back to your default branch and if you want to resume  
work just go back to the bookmark (and optionally merge with updated  
default)

I'd probably go for the latter since I often use mq and sometimes  
shelve (didn't know about tasks until Mike's post).


More information about the Mercurial mailing list