NOTE: These comments are only somewhat associated with your design. I
have wanted to add better integration of Subversion with Issue Tracking
systems and thought revision properties would be a good way to store this
information. So these comments are based more on the usage of rev props.
Daniel Berlin <dberlin@dberlin.org> wrote on 04/28/2006 12:34:04 PM:
> 1. Need to be able to set a revprop to be stored on commit
You should potentially see:
http://subversion.tigris.org/issues/show_bug.cgi?id=1976
It would be nice if the general capability in that issue were added at the
same time.
> 3. Need to be able to have auth treat SVN_MERGE_PROPERTY revprop
> differently from other revprops (either by special casing the cases
> users do care about controlling, or special casing props users don't
> care about controlling, etc) so that people who don't have access to the
> revprops can still do history sensitive merges of directories they do
> have access to.
Depending on how you implement this you might also need to take hooks into
consideration since revprops cannot be changed without the hook enabled. I
would assume from #1 that you would build setting the revprop into the
commit transaction so there would be no more need to change this revprop
then something like svn:log.
Since revprops are not stored in the WC, where would this info be stored
so that commit would know how to include it? Maybe commit copies the
previous revprop and adds the new info to it?
> Random questions and answers
> Can we do without the revprop portion of this design?
> Technically yes, AFAIK, but it may require more crawling and querying at
> merge time.
I am not sure why this would be true. Revprops are not stored in the WC,
so won't this require a lot of repository access to retrieve the revprops?
Or do you envision all of this happening on the server anyway?
Thanks
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 28 19:18:46 2006