kfogel@collab.net wrote:
>For 1.3, we've been talking as though log message templates
>unquestionably depend on coming up with some sort of generic
>server->client configuration transmission mechanism.
>
>
You know, I'm totally against adding a server->client transmission
channel that's useful only for log message templates. Whatever we decide
to do, even if it's only *used* for log templates in 1.3, must be
designed so that the same mechanism can be extended for other uses.
Otherwise we're headed for the proverbial maze of twisty little
passages, all alike.
[snip]
> I don't know if this hook should have a way of stopping the
> commit, the way pre-commit does; my instinct is it shouldn't,
> because it has the option of sending back a template that just
> tells the committer to consider aborting because he's committing
> in an incoherent set of directories. But whatever, that's a
> minor question to be settled in later discussion.
>
>
We already have pre-commit hooks that can abort the commit.
>Anyway: no server->client configuration transmission mechanism here.
>
>
Eh? What is this if it isn't a server->client configuration transmission
mechanism? That you want to implement it with a hook doesn't change that. :)
>The main thing I wanted to do is separate "Log Message Templates" from
>"Server->Client Config Transmission". One is the feature users
>actually want; the other is *a* way to implement it.
>
>
Users also want to be able to define autoprops on the server, either
per-repository or per-directory. The problems are much the same as with
log message templates, except that you'd have to somehow get at
autoprops when you "svn add", not when you "svn commit".
In fact, the feeling I get from reading users@ (without actually
counting messages) is that server-side autoprops are more important than
log message templates...
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 17 11:02:58 2005