-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2008-Jan-09, at 11:57, kmradke_at_rockwellcollins.com wrote:
>> That's a *revision* property, not a file property. Revision
>> properties apply to the entire commit (svn:log, svn:author, and
>> svn:date are the only ones that come to mind). The initial question
>> in this thread was about a file property, which can't be changed the
>> same way as a revprop.
>
> I realized this. I believe you can add arbitrary revision
> properties. It would take more information stored in the
> revision property, such as a filepath/version combo, but it should
> still be possible (albeit highly unrecommended).
It's possible I misunderstood the original thing you were trying to
do, so just to clarify... as I understand it you're trying to
implement per-file version numbers, right? So.. whenever file X gets
modified, some property with a number in it gets advanced. Is this
correct?
If so, then advancing that number when its stored in a revision
property is going to be a more complex task. You can't just retrieve
the number by looking at the HEAD revision of that file.. you'll need
to search back through the repository for the last time the file was
modified, get that revision number, look up your custom version
number from the revprop on that version, and then modify the revprop
on the HEAD.
Not impossible, but you're looking at a lot of work to do something
you probably don't want to do anyway. :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)
iD8DBQFHhQFHmFeRJ0tjIxERAkuqAJ0VNzk11IXtRDnfC4zgMR7uc4CZXgCfRWH9
4/BnvXIhFZit5e0tyCgYLEI=
=EXI9
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-09 18:16:22 CET