简体   繁体   中英

hg revert or update to browse commits and then change back to newest?

If your just want to compile and run some code then go back without any changes what's standard practise? (EDIT: assume the parent is at tip to begin with)

hg revert -C -r 0 --all

hg revert -C -r tip --all

OR

hg update -C -r 0

hg update -C -r tip

I'm ok with deleting uncommitted stuff (-C) but is there any prefered way. Also annoyingly tortoisehg doesn't seem to do the revert workflow with a click any ideas? http://comments.gmane.org/gmane.comp.version-control.mercurial.tortoisehg.user/2728

PS I know update move's the parent and revert does not.

Update is the better choice. That way if you forget and make a code tweak you're in a position to commit it, possibly creating a new head, which is okay.

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM