On Tuesday 2008 December 30 20:30:46 Conor Rafferty wrote: > MERCURIAL: > > Update > hg update [-C] [-d DATE] [[-r] REV] Which is the role of "git checkout <branch>" "git checkout <branch> <paths>" is similar to "hg revert -r <branch> <paths>", but the later seems to handle your use case properly. I don't know much about the workings of hg revert -- it might use the history to determine what's correct, or completely bypass the existing "index" when determining what to drop. In any case, it seems to work better for what you are trying to do. Why not just use it? I could do with more hg/bzr/darcs experience myself, but git seems to behave the way I like it so it's what I use. When deciding on the right tool for the job, it does help to have many. "To the man with only a hammer, all problems look like nails." That said, I'm pretty sure that if you hasn't specified '.' and just used "git checkout <branch>" you wouldn't have seen those "artifacts". -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@xxxxxxxxxxxxxxxxx ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
Attachment:
signature.asc
Description: This is a digitally signed message part.
