[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Merge tracking feature request

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Wed, 18 Jun 2008 18:24:05 +0200

Robert Dailey wrote:
> On Wed, Jun 18, 2008 at 11:12 AM, Stefan Küng <tortoisesvn_at_gmail.com
> <mailto:tortoisesvn_at_gmail.com>> wrote:
>
> Robert Dailey wrote:
>
> Hi,
>
> I noticed when I create a feature branch, there is no default
> svn:mergeinfo set. For example, if my trunk is at revision 100,
> and I create my feature branch from that revision, the default
> property for my working branch root should be:
>
> /trunk:0-100
>
> on my new feature branch. Why is this not the case? This would
> be extremely helpful, as I won't have to remember in my head (or
> have to put it in my branch log) which revision I branched from.
> Would this be a difficult feature to add?
>
>
> To get the revision from where you branched, use the log dialog.
> There's a checkbox "stop on copy". If enabled, the log will stop at
> the point where you created the branch.
>
>
> You're saying to "show log" on my branch or on trunk? I'm assuming you
> mean the branch. This does work, but it doesn't help me in the merge
> dialog, because the "Show log" button in the merge dialog shows the log
> of the branch I'm merging FROM, which is the trunk. And from that
> location, you cannot tell where you branched from.
>
> Is there a reason why the svn:mergeinfo doesn't start out with 0-100 (as
> in my last example)? What would it hurt to make it do this?

You'd have to ask on the Subversion mailing list. TSVN does not even
touch the svn:mergeinfo properties itself.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net

Received on 2008-06-18 18:24:25 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.