What to do befor "hg update"

[Robert Bauck Hamar]

*Roland Schmitz:
>Hello everyone,
>
>i'm new to mercurial, but i think, this could be my tool for version 
>management ;-}
>As far as i'm today, i found that i can ask mercurial what it will do. Before 
>doing a hg pull i'll run hg incomming, ...
>hg push/hg outgoing
>hg commit/hg status
>But i havent found which command will tell me what hg update will do.

$ hg parents
... get revision id, say 42
$ hg diff -r 42 -r tip
... patch hg update would apply.

Replace tip by some other revision if your updating to some specific 
revision.

Note, that if you have uncommited changes in your working directory, the 
diff won't show them. Is there anything that would show this merge 
result as well? However, you should avoid updates where this is complex:

* Commit the changes before update if you have some.
* If there are some config files or such you would have to edit to run 
the code from the working dir, use a different name for the versioned 
templates.

-- 
Robert Bauck Hamar
USIT/SAPP/GT - Cerebrum
http://www.uio.no/sok?person=hamar
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial/attachments/20090708/972da9c6/attachment.pgp