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

Re: svn:mergeinfo suggestion

From: Robert Dailey <rcdailey_at_gmail.com>
Date: Wed, 18 Jun 2008 15:26:59 -0500

On Wed, Jun 18, 2008 at 3:23 PM, Erik Huelsmann <ehuels_at_gmail.com> wrote:

> On Wed, Jun 18, 2008 at 6:34 PM, Robert Dailey <rcdailey_at_gmail.com> 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?
> This use case was covered way before we ever even started adding merge
> tracking:
> $ svn log -q --stop-on-copy URL-OF-FEATURE-BRANCH
> and have a look at the output...

Well, I knew I could look at the log of the feature branch to find out what
revision I branched at, but having the svn:mergeinfo set by default would be
even quicker and more intuitive. If you have a very developed feature
branch, it could take a very long time to load the log and shift through it
simply to just find the last revision. Are you objecting to the change I am
suggesting? If so, why? Why would setting svn:mergeinfo to a default of
0-branchrevision be so bad?
Received on 2008-06-18 22:27:39 CEST

This is an archived mail posted to the Subversion Users mailing list.

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