On 02.01.2012 09:34, Mark Mielke wrote:
> On 01/02/2012 02:52 AM, Alan Barrett wrote:
>> On Sun, 01 Jan 2012, Mark Mielke wrote:
>>>> Another idea is to change the revprop's value in the pre-commit or
>>>> post-commit hook: [...]
>>>
>>> This is what we've been doing for about two years. It has the
>>> consequence that tools don't automatically match unique identifier
>>> to commit as they no longer match.
>>
>> If your third party tools can't extract the unique ID from svn:author
>> = "Display Name <uniqueid_at_domain>" then perhaps the problem lies at
>> least as much in your third party tools as in subversion.
>
> I wonder if you thought this through before posting. :-)
>
Hi Mark,
I only loosely followed this thread but I still want
to throw my 2 cents in here.
It seems that you are looking for a formal way
(i.e. accessible to tools) to identify the "author"
of a change and you listed some problems that
you are facing with the current state of things.
To me, it seems that there actually *is* plenty room
for improvement and simply nobody really brought
the topic up until now.
If you are working towards a proposal (problem
description + proposed solution), make sure you
start your analysis at the very basic. Such as:
* What is an author?
* How do concepts like "account", "person",
"role", "group" relate to that notion?
* What aspects of the above can be provided to /
handled by Subversion in a portable way?
* What are typical use-cases and do they match
with the definitions you use?
> svn:author => unique identifier
That seems to be the hardest to define and may
be difficult to provide. Identifies the person?
PGP key ID?
> svn:author-name => Mark Mielke
That would denote the "person". How would
duplicates and name changes be handled?
> svn:author-email => mark_at_mark.mielke.cc
That looks close to the "account" aspect.
-- Stefan^2.
Received on 2012-01-03 04:03:25 CET