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

Re: can of worms: custom props in our tree?

From: John Peacock <jpeacock_at_rowman.com>
Date: 2003-11-05 19:39:06 CET

Ben Collins-Sussman wrote:
> And to top it all off, he's even doing
> some degree of "smart merging", i.e. using properties to track merges.
> Really impressive stuff.

That's so cool! Too bad I didn't suggest it before he started work on it so I
could take credit for it. ;~)

> But here's the rub: when svk commits, it sets a custom property that
> records some merge tracking data. It looks like this:
> svm:source = ae6c956b-9dc6-0310-97b2-e73af4192982:/svn/local:6908

That's guid, path, last revision number, right?

> Now, as far as Subversion is concerned, this is a "user" property. It
> may as well be "color = green". It's not in the svn: namespace, so it's
> just random user data.

But if this model works out, there will be an eventual 'svn:mergepoint'
property, right? And a script to convert an existing branch?

> The question is, are people going to freak out if they see a property
> like this appear in our tree? Most people seem to have an initial gut
> response of "ewww, get that crap out of our tree".

I would so like to have this feature! One big project I have brewing requires
me to have a very long-lived private branch of the Perl source code, and I need
to repeatedly merge changes from TRUNK to my branch. It is currently a very
manual operation (I have to find the right PostIt(tm) with the last merge ;~).


John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 5 19:39:32 2003

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

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