On Thu, Aug 16, 2012 at 4:46 PM, Cedric JP. Brasey
<cedric.brasey_at_planet-side.co.uk> wrote:
> Just my two pence worth...
>
>
>
> From a hooking point; I would have to say that i would only really care
> about what the client level is. For example. On pre-commit i would like to
> know if the client is at least 1.7, so that I can then reject the commit. I
> can't imagine, for the mo anyways, any scenario where i would care if this
> is a windows client, svn kit, etc.
>
>
>
> From a server point; I would imagine that this would be like the preverbal
> pot 'o gold. You could introduce new functions with the assurance that the
> client is of the correct spec. Backwards compatibility would also be easier
> with the introduction of a 'minimum level' for the methods...
It can also be important to know what client it is and its version,
not just the svn library version.
For example:
TSVN has client-side hooks, which can be used to run e.g. a full test
suite before a commit, or run a script which checks whether the user
has run all required tests.
Now, the server hook script might want to check whether the user
actually uses TSVN, and with a version that executes those client-side
hook scripts.
Only if e.g. TSVN is used with version > 1.8.0 then the hook script
allows the commit because it only then can assume that the commit only
happens if the tests were run.
So, if we can give that info back to the hook script, then we should do so.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2012-08-16 17:22:38 CEST