Daniel Rall wrote:
> On Wed, 03 Oct 2007, Kamesh Jayachandran wrote:
>
>>>> NOTE: The above command does not accept a revision range.
>>>>
>>>> I would like to confirm whether this is a bug before I can file a issue
>>>> for this in s.t.o
>>>>
>>> I cannot envision what it ought to do with the -r argument. Is this a
>>> case of all subcommands getting the -r argument automatically unless
>>> they do something specific to reject it?
>>>
>>>
>> We may not need -rstart:end but we may need it for one revision. Just to
>> see what was the mergeinfo on {2007-10-03}.
>
> Yup, we -r -- or need something like it -- to support a peg revision
> for the 'mergeinfo' command.
Right. -r is part of the full implementation of the
peg-and-operative-revision syntax we try to support universally. It's use
in this scenario? Asking about mergeinfo on something that's not HEAD or in
the working copy.
--
C. Michael Pilato <cmpilato@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on Tue Oct 9 18:42:59 2007