You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Senthil Kumaran S <se...@collab.net> on 2007/10/03 09:45:24 UTC

svn mergeinfo '-r' option

Hi,

I tried using "svn mergeinfo" command and could not get the usecase of 
'-r' option.

I tried the following and in all the cases "svn mergeinfo" command 
behaves in the same way.

<snip>
$ svn mergeinfo
Path: .
   Source path: /trunk
     Merged ranges: r0:26218, r26233:26405, r26463:26468
     Eligible ranges: r26218:26233, r26405:26463, r26468:26903

$ svn mergeinfo -r 454454
Path: .
   Source path: /trunk
     Merged ranges: r0:26218, r26233:26405, r26463:26468
     Eligible ranges: r26218:26233, r26405:26463, r26468:26903
</snip>

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

Thank You.

--
Senthil Kumaran S
http://www.stylesen.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn mergeinfo '-r' option

Posted by Kamesh Jayachandran <ka...@collab.net>.
Senthil,

mergeinfo subcommand should support '-r' option.

With regards
Kamesh Jaychandran


Senthil Kumaran S wrote:
> Hi,
>
> I tried using "svn mergeinfo" command and could not get the usecase of 
> '-r' option.
>
> I tried the following and in all the cases "svn mergeinfo" command 
> behaves in the same way.
>
> <snip>
> $ svn mergeinfo
> Path: .
>   Source path: /trunk
>     Merged ranges: r0:26218, r26233:26405, r26463:26468
>     Eligible ranges: r26218:26233, r26405:26463, r26468:26903
>
> $ svn mergeinfo -r 454454
> Path: .
>   Source path: /trunk
>     Merged ranges: r0:26218, r26233:26405, r26463:26468
>     Eligible ranges: r26218:26233, r26405:26463, r26468:26903
> </snip>
>
> 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
>
> Thank You.
>
> -- 
> Senthil Kumaran S
> http://www.stylesen.org/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn mergeinfo '-r' option

Posted by "C. Michael Pilato" <cm...@collab.net>.
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 <cm...@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand


Re: svn mergeinfo '-r' option

Posted by Daniel Rall <dl...@collab.net>.
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.

Re: svn mergeinfo '-r' option

Posted by Kamesh Jayachandran <ka...@collab.net>.
>> 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}.

With regards
Kamesh Jayachandran

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn mergeinfo '-r' option

Posted by Mark Phippard <ma...@gmail.com>.
On 10/3/07, Senthil Kumaran S <se...@collab.net> wrote:
> I tried using "svn mergeinfo" command and could not get the usecase of
> '-r' option.
>
> I tried the following and in all the cases "svn mergeinfo" command
> behaves in the same way.
>
> <snip>
> $ svn mergeinfo
> Path: .
>    Source path: /trunk
>      Merged ranges: r0:26218, r26233:26405, r26463:26468
>      Eligible ranges: r26218:26233, r26405:26463, r26468:26903
>
> $ svn mergeinfo -r 454454
> Path: .
>    Source path: /trunk
>      Merged ranges: r0:26218, r26233:26405, r26463:26468
>      Eligible ranges: r26218:26233, r26405:26463, r26468:26903
> </snip>
>
> 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?

-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org