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

Re: Storing Copied-To info (was: Tree conflicts - thoughts on use cases, merging, and tests)

From: Mark Phippard <markphip_at_gmail.com>
Date: Fri, 21 Mar 2008 08:11:51 -0700

On Fri, Mar 21, 2008 at 7:51 AM, Stefan Sperling <stsp_at_elego.de> wrote:
> On Fri, Mar 21, 2008 at 09:46:55AM -0400, C. Michael Pilato wrote:
> > But I actually question the conclusion you provide for your own use-case.
> > Yes, an issue tracker can tell you which branches have had a bugfix
> > applied. But that's rather dependent on your processes involving a
> > tracker, and on human ability to keep said tracker up to date, and must be
> > cross-referenced with the version control system anyway to answer the
> > similar question, "In which branches has this bugfix *not* been applied?"
> The question is "How much of a process-management tool vs. a version control
> system (which provides a subset of the functionality of the former) does
> Subversion want to be?" Or maybe it is "How much does Subversion want to help
> process-management tools with organizing their data?"
> The line has to be drawn somewhere.

I want the line to be within a revision graph :)

Seriously, this feature is asked for a lot. I was just at EclipseCon
this week and it comes up over and over again when talking about SVN.
The hacks you have to do today to create one of these are crazy and it
would be great if the repository could just provide the information
needed for this to become a first-class feature of SVN.

We also have this feature in Subclipse that could probably use this
information if it existed:


Mark Phippard
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-21 16:12:02 CET

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