annotations / properties per revision / checkin, not per file

[Stefan Seefeld <se...@sympatico.ca>]

hi there,

Is it possible to associate a property with a checkin
and not with a file ? I'd like to establish some communication
between subversion and an issue tracker, but all I'v come up
with so far is embedding a tag into the checkin comment and
then filtering it out from within the pre-commit script.
Is there a more elegant solution to this (seemingly common)
use case ?

Thanks,
		Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

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

[kf...@collab.net]

Ben Collins-Sussman <su...@collab.net> writes:
> I'm not sure what you mean... Subversion already has this.  Files and
> directories have versioned properties attached, but a revision tree
> can also have arbitrary 'properties' attached directly to it... see
> chapter 5 in the book, "unversioned properties".  The commit log
> message itself is an unversioned property attached to a revision tree.
> So is the author and datestamp.  You can make up any revision
> properties you want.

Just to clarify:

"unversioned property" and "revision property" are synonymous.  It is
a property attached to the revision itself, instead of to an object
inside the revision tree.  Sometimes these properties are called
"revprops" for short.

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

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

[Ben Collins-Sussman <su...@collab.net>]

On Dec 9, 2004, at 11:59 PM, Stefan Seefeld wrote:

> hi there,
>
> Is it possible to associate a property with a checkin
> and not with a file ?

I'm not sure what you mean... Subversion already has this.  Files and 
directories have versioned properties attached, but a revision tree can 
also have arbitrary 'properties' attached directly to it... see chapter 
5 in the book, "unversioned properties".  The commit log message itself 
is an unversioned property attached to a revision tree.  So is the 
author and datestamp.  You can make up any revision properties you 
want.


> I'd like to establish some communication
> between subversion and an issue tracker, but all I'v come up
> with so far is embedding a tag into the checkin comment and
> then filtering it out from within the pre-commit script.
> Is there a more elegant solution to this (seemingly common)
> use case ?
>

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.

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.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org