Re: [Monotone-devel] [PATCH] head selector

[Brian Downing]

On Sun, Jun 26, 2005 at 07:36:42PM +0200, Richard Levitte - VMS Whacker wrote:
> In the particular case you mentioned ('monotone update -b {branch} -r h:')
> I still do not see why there should be a need to specify the head
> revision either way.  Can you see another command where having to
> specify that you want the head of the branch given in --branch makes
> sense?

The current update behavior without a revision is to do something like
"update to the newest decendent of the current revision limited to ones
in the specified branch."  If you want to update "backwards" in the tree,
you need to specify a revision explicitly somehow.

(from the head)
:; cat MT/revision
3d25bb6fb3d415a91c27841b90eda9c9d6338af4
:; monotone update -b net.venge.monotone.cvssync
monotone: already up to date at 3d25bb6fb3d415a91c27841b90eda9c9d6338af4
:; monotone update -b net.venge.monotone.cvssync -r h:
monotone: expanding selection 'h:'
monotone: expanded to '7b88f7c9b843cae0b068b5232edf812c9b2b367d'
monotone: selected update target 7b88f7c9b843cae0b068b5232edf812c9b2b367d
...

Diff has the same problem:

:; monotone diff -b net.venge.monotone.cvssync
#
# no changes
#
:; monotone diff -b net.venge.monotone.cvssync -r h:
monotone: expanding selection 'h:'
monotone: expanded to '7b88f7c9b843cae0b068b5232edf812c9b2b367d'
...

Maybe this should be considered a bug...

-bcd