David Weintraub <firstname.lastname@example.org> writes:
> That's not a bad idea. Not too sure how to do that though. Do I simply
> put a link to this thread in the comments of the bug?
Yup. You need to be logged in as an Observer on
subversion.tigris.org, which if you don't have that role already will
(unfortunately) require you requesting it and then someone approving
you. But that usually happens pretty quickly.
> It took me a while to parse the code (Hey this isn't written in Turbo
> Pascal!) , but I did find a few things. The libsvn_wc doesn't have
> anything in it for handling revision properties. In order for the "svn
> setprop --revprop" command to be able to track and set revision
> properties, the libsvn_wc must be modified. A way of storing these
> properties in the .svn directory is also needed. This means that the
> bindings don't work. Well, they do work, but they cannot set a
> revision property before it is committed to the archive. I was
I don't see why the revprops would need to be stored in .svn/ at any
> However, the libsvn_ra library does have the ability to set revision
> properties during a commit. This make sense since svn:log, svn:author,
> and svn:date all are revision properties that must be set before the
> commit takes place. However, from what I can tell, the libsvn_ra
> library seems to gather the data for these three revision properties
> The basic communication infrastructure is there, and the ability to
> set revision properties during the commit process would add a lot of
> value to Subversion (especially if you could easily search for those
> properties). Unfortunately, it would involve changing the way data is
> stored in the .svn directory, and modifying libsvn_wc and
> libsvn_client to handle this issue.
Well, Subversion already has the 'svn propset --revprop'
functionality. This would just be another pathway to that same
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Jun 23 01:18:52 2005