Trouble is: changing the revisioned properties also changes the revision of the file.
Example: I am working on a file foo.c. I committed the file foo.c a while ago, added changes in other files lately and would now like to store information about the peer review I just carried out with my colleagues.
The repository meanwhile has been propagated to revision 50.
I would like to store the information "foo.c rev. 44 was peer reviewed and no anomalies were found" as a revisioned property.
Jack suggested to make the revision part of the property value. So lets say I have a property called "PEER_REVIEW" and I change the value to "44_OK". But this changes the last changed revision of foo.c to 51.
At the end of the implementation phase, I would have to prove that revision 51 of this file is equal to revision 44 in which the file content was last changed.
> Thank you for all the good ideas. There are some considerations I will start with:
> - Jack Repennings hint of simply making the revision part of the property value.
> - Greg Steins advice for a pre-commit hook to ensure that all changed files have a reset property
> - and B Smith-Mannschott's idea to use the checksum as "invalidator".
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1095841
Received on 2009-02-03 10:39:32 CET