> Erik Huelsmann points out that the right way to do this is not by the
> client's name, but by it's desires, e.g.:
>
> --xml ## send the template in xml
> --mime-type=blah ## send the template with blah mime-type
> --path-list-incomplete ## this path list is not complete
>
> (The --path-list-incomplete would for TSVN and others to use.)
>
> Again, this is a matter of shipping a good default hook script that
> knows how to handle these things, so that they become standards.
That is essentially what I proposed as well. I proposed that TSVN be able
to invoke the hook without passing any of the paths. It would have to be
documented for hook providers to be aware of this. I further suggested
that if the hook provider ultimately wanted to have the list of paths in
the commit message, there could be an agreed-upon substiution variable
placed in the template that the hook returns to the client, such as
$FILES$.
TSVN could then have a button to replace the variable with the file list
and/or do it automatically when the user submits the commit.
If we go down this path, then I think that Subversion (the project) should
dictate the name of the variable(s) and for the list of files it should
also dictate what that should look like so that if there are multiple GUI's
they all do it the same way.
Just as an example, I have seen people list the files in both these
formats:
A path/filename
M path/filename
D path/filename
Added path/filename
Modified path/filename
Deleted path/filename
TSVN currently even substitutes non-English equivalents.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 26 02:41:55 2005