[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: Stefan Sperling <stsp_at_elego.de>
Date: Fri, 21 Mar 2008 15:51:06 +0100

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 began work some time ago on successor link support on a branch with a
> related name (fs-successor-ids, perhaps?). I don't recall the status of
> that code -- probably something like "BDB stores it, but you can't use it;
> FSFS lacks a design altogether."

Now I remember you mentioning this branch in the past. Quite interesting.
I guess Talden might want to take a look at that branch :)

-- 
Stefan Sperling <stsp_at_elego.de>                 Software Developer
elego Software Solutions GmbH                            HRB 77719
Gustav-Meyer-Allee 25, Gebaeude 12        Tel:  +49 30 23 45 86 96 
13355 Berlin                              Fax:  +49 30 23 45 86 95
http://www.elego.de                 Geschaeftsfuehrer: Olaf Wagner

  • application/pgp-signature attachment: stored
Received on 2008-03-21 15:51:08 CET

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