Mike Kupfer writes:
Also, which repository are you pulling from: xemacs-beta or xemacs?
Pushes to xemacs age for a bit before being pushed to xemacs-beta. You
can use "hg path default" to get the answer.
We'll see if Ben is going to produce enough churn to make it worth
maintaining xemacs-beta. For now using the xemacs branch is
recommended, until you actually experience unacceptable breakage.
Here's why "pull" and "update" are separate:
This is actually a UI bug, IMO. It makes a lot of sense for *push*
and update to be separate, because that allows a workspace-less repo
on servers. But there's very little point in making pull and update
separate, since the common case is "hg pull; hg update", not "hg pull;
manipulate revisions vs. the existing workspace; hg update". What's
even weirder is that the "hg fetch" extension does this (plus some
frills), giving hg commands nearly the exact opposite of git's.
I use "hg pull -u" ("pull and update if clean") as a matter of habit.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta