On 01/08/2012 09:55 PM, Stefan Fuhrmann wrote:
> On 04.01.2012 19:42, Julian Foad wrote:
>> The extended author fields are delivered through revision
>> properties. The values are UTF-8 text. These revision properties
>> are readable but not writable by clients.
> Maybe, I missed something in your post but I want
> to stress that is very important to be able to change
> that information later on.
The idea that Julian put forward is that these would be calculated
fields. Never stored. Always "fresh" (beyond allowance for server side
caching configured according to requirements).
I think this is perfectly adequate for all use cases I can think of.
However, it does mean that historical users need to be maintained within
the server-side database that is used to calculate the field values.
Any fields which are truly per-commit and not per-user, are not
svn:author fields. They are something else. Per-user fields can stay as
"latest" or if there is ever a scenario where a user must have an "old"
identity and a "new" identity, this could be accomplished by having the
user change their unique identifier allowing both old- and new- mappings
to remain valid.
Received on 2012-01-09 04:49:13 CET