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

Re: annotations / properties per revision / checkin, not per file

From: Stefan Seefeld <sseefeld_at_art.ca>
Date: 2004-12-10 14:58:19 CET

Ben Collins-Sussman wrote:

> People often have the pre-commit hook program do a search for an
issue-number in the commit log message, as you're doing.
> The post-commit hook is a more common place to do it, though... that's
typically the best time to notify the issue tracker
> that some relevant commit happened.

right, though if you want to audit the ckeckin, i.e. block it depending on
issue- or revision-specific characteristics,
you have to put it into the pre-commit script.

> At this time, there's no way to make 'svn commit' create arbitrary
unversioned properties on the transaction tree before its > promoted to a
revision tree. That's just an oversight in our UI, perhaps. Though, 'svn
propset/propedit' are able to change
> unversioned properties on -finished- revision trees. Not sure if that
helps you.

Now I understand why I didn't find unversioned properties. Yes, I believe
having something like 'svn co -p foo=bar ...' where
property 'foo' is set to 'bar' would be a very useful addition. That's more
than a convenience, I believe, as it enables me
to treat annotated checkins atomically, i.e. use customized properties for
the issue tracker. I'd rather not embedd any
metadata into the log, so this will remain fully targetted at human readers.

Should I file an enhancement request for this ? How involved would an
implementation be ?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 10 18:32:06 2004

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

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