[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 14:22:21 +0100

On Sat, Mar 22, 2008 at 01:37:12AM +1300, Talden wrote:
> Note that this probably doesn't make looking for copied-to information
> cheap, but I think that for many use-cases it will make it cheaper.

I'd like to see concrete use cases to support a copied-to implementation.
As stated in another mail in the thread this one has spawn off from,
I've implemented this once for a client, using properties to store the
copied-to info (which isn't a good design but works as a proof-of-concept).
The use case this was going to support was "given fix for a bug, how I can
find out on which branches this fix has been applied to already?".
This use case is invalid IHMO because it can be answered more effectively
by an issue tracker than Subversion itself. The client even ended up not
using the code.

Do you have other use cases that would benefit from having copied-to
information available?
 
> Would this be useful in building
> revision graphs that trace tagging and branching as well as
> modification?

Yes, I think it would. This is one valid, albeit exotic, use case already.

-- 
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 14:21:56 CET

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