On Wed, 2004-07-28 at 04:18, Martin Tomes wrote:
> My preference is for an additional property in the svn: namespace called something like
> svn:requiredprops which lists properties which are required to be set for this file.
Note that a pre-commit hook can enforce this sort of thing. But that's
only a small part of the problem:
> The client
> would then list those properties in the commit message editor (as Kristis Makris proposed in this
> thread) with their current values and then set them before commiting. The command line client would
> put them in the text sent to the users text editor, a GUI could show them as name/value pairs on the
> commit form.
[...]
> Should I add this text to the issue?
I don't think so; the issues relevant to this thread are nice and
contained (log message templates, rev-props on commit); what you're
talking about is a change to the way file properties are handled. So I
don't think either issue is directly related to your needs.
While I understand that our operational model for file properties
doesn't quite meet your needs, your needs seem specific enough that they
are probably best met through custom UI development. We have to keep
our operational model simple enough that it's easily understood by all
users, even if that means not all workflows can be trivially mapped onto
it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 28 18:20:56 2004