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

Re: Parseable tracking of code contributions.

From: John Belmonte <john_at_neggie.net>
Date: 2005-07-15 14:06:02 CEST

kfogel@collab.net wrote:
> Duane Griffin <d.griffin@psenterprise.com> writes:
>>On Wed, 2005-07-13 at 16:44 -0500, kfogel@collab.net wrote:
>>>Let's use a parseable format in log messages, for recording code
>>>contributions, analysis, and review.
>>In an ideal world, wouldn't it be better to record those sort of things
>>in revision properties? It would have all sorts of benefits which I
>>guess are pretty obvious to people here. My understanding is that
>>limitations in the svn interface make it hard to use revision
>>properties, but perhaps those could be addressed?
> The benefits of using revision properties other than svn:log are not
> obvious to me, at least; whereas the advantages of using svn:log are
> -- the data shows up in 'svn log' output! :-)

I think it's unfortunate that custom properties are not used in the
Subversion repo. If you had tried to use them a while back, I bet we
would already have essential features like being able to set commit-time
revision properties from the command line, being able to display a given
set of custom revisions properties in svn log, automatic merging of file
properties, and being able to revert file contents and file properties
independently of each other. If these aren't pain spots for you, then
you aren't relying on custom properties.

--Regards, John

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 15 14:06:51 2005

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.