Ryan Schmidt <subversion-2009a_at_ryandesign.com> wrote on 01/14/2009 09:33:49
PM:
> "Subversion increments the revision number of the repository as a
> whole, so it can't expand any keyword to be that number - it would
> have to search and possibly modify every file in your working copy on
> every update and commit."
>
> To expand on that, I think it means that on every update and commit,
> Subversion would have to look at the svn:keywords property of every
> file in your working copy to see if it uses the BiggestRevision
> keyword, and if so, replace the revision in that file. That would
> probably slow things down drastically as Subversion would have to
> read many more prop-base files than before to make this
> determination. And this performance issue would affect everybody, not
> just those using this new keyword.
I for one would be willing to incur the penalty, which my intuition says
is small compared to the time to write the files. I can grep for
$GolbalRev$ in my entire code tree sub-second. How long could it
take to search some meta-data?
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1029207
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-27 21:41:27 CET