You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Daniel Berlin <db...@dberlin.org> on 2006/07/07 11:42:18 UTC
Re: suggestion about the merge-tracking branch
Madan U Sreenivasan wrote:
> Hi,
>
> This is about the merge-tracking code.
> Am wondering why 'merge' insists on a revision range on the command
> line. If for example the user wants to merge r12, it implicitly means
> r11:12. Why cant this be generated?
It is, if you use -c
svn merge -c 12 will do what you want.
> Why should we put the burden on the
> user?
Eventually in fact, the minimum is that we shouldn't require a revision
range at all, just a url, since we can figure out the rest on our own
with merge tracking info.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: suggestion about the merge-tracking branch
Posted by Madan U Sreenivasan <ma...@collab.net>.
On Fri, 07 Jul 2006 17:12:18 +0530, Daniel Berlin <db...@dberlin.org>
wrote:
> Madan U Sreenivasan wrote:
>> Hi,
>>
>> This is about the merge-tracking code.
>> Am wondering why 'merge' insists on a revision range on the command
>> line. If for example the user wants to merge r12, it implicitly means
>> r11:12. Why cant this be generated?
>
> It is, if you use -c
>
> svn merge -c 12 will do what you want.
will try it out. Thanks!
>
>> Why should we put the burden on the
>> user?
>
> Eventually in fact, the minimum is that we shouldn't require a revision
> range at all, just a url, since we can figure out the rest on our own
> with merge tracking info.
+100. :)
Regards,
Madan.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org