commands: hg clone update priority

[timeless]

On Sun, Mar 7, 2010 at 5:39 PM, Greg Ward <greg-hg at gerg.ca> wrote:
> The commit message should mention that this is only docs and tests.
> (I.e. this probably belongs in stable, if the test is solid.)

helpwanted. i'm not very good about commit messages (or trying to get
into stable)

> That's not what I observed with 1.5, unless "empty" does not mean what
> I think it means.  I cloned a repo with no working copy (parent =
> null), and hg checkout a working copy in the new clone.

Empty was supposed to mean 'remote repo has 0 revisions'

> "if run with -u . and the source repository is local, the first parent
> of the source repository's working dir"

wow, that's long, ok.

> "the changeset specified with -u (if a branch name, this means the
> latest head of that branch)"

i have concerns about 'latest' (we mean topological something-or-other)

> "the changeset specified with -r"

thanks

> "the tipmost head of the branch specified with -b"
...

> IOW: branches don't have tips, they have heads.  There is only one tip.
>
> I'm neutral on "tipmost" vs "latest".  "Latest" is more conventional
> English, but it could be interpreted as chronological.  That's
> presumably why most hg help uses "tipmost".

we didn't like 'head' as there can easily be more than one. i don't
dislike tipmost.

> I'm also neutral on "-r" vs "-r/--rev".  I've left out the long form
> in my recommended edits just to see how it looks.  Please adjust as
> you see fit.

I really do want to address that at some point, but arguably that
point shouldn't be today.