fu> # nooo mercurial still doesn't have a way to distinguish between the patch author and committer
Yes, very true. Is this important?
pull and remove bookmark should not cause merge.
amending commits is not going to work for a centralized repo for either git or hg. once you push, you'll have that changeset sitting there looking malformed at you. someone will have to do central repo surgery. (looks over at github repo sadly)
git index is imo a pain
bookmarks do float upwards on commit, like branches.
hg exposes bookmarks poorly in general imo. that is part of why I suggested mixing branches and bookmarks, so that dev and prod can be kept very separate.
no subject
Yes, very true. Is this important?
pull and remove bookmark should not cause merge.
amending commits is not going to work for a centralized repo for either git or hg. once you push, you'll have that changeset sitting there looking malformed at you. someone will have to do central repo surgery. (looks over at github repo sadly)
git index is imo a pain
bookmarks do float upwards on commit, like branches.
hg exposes bookmarks poorly in general imo. that is part of why I suggested mixing branches and bookmarks, so that dev and prod can be kept very separate.