On Tue, 2005-11-08 at 22:07 -0600, kfogel@collab.net wrote:
> When you commit, the client contacts the server with a new RA call,
> propget_walking_upward().
I think some perspective is in order here. Right now we have a number
of present and future features which involve settings with the following
qualities:
* They might vary between directories in a repository.
* Most of the time, they don't vary between lots of directories.
These features include:
* (Present) svn:ignore
* (Future) Repository-specified auto-props
* (Future) Log message templates
* (Future) Easy branch comparisons
(Log message templates have the added issue that it's ambiguous what to
do when you have a commit across multiple directories with different
templates. But that's just a matter of choosing semantics, and is
mostly irrelevant.)
Arguably, we haven't implemented any of the future features *because* of
the clunkiness of directory properties which mostly don't vary between
lots of directories. It's very tempting to try to solve this clunkiness
in a feature-specific way, because it lets you get the feature done
without having to solve anything hard. But I think that would be a
mistake; even if our eventual iprops mechanism winds up being a little
ugly and having some corner cases which are hard to get right,
Subversion will be more elegant overall if we don't take a narrow view
of the problem.
However, to solve the general problem, we need a solution which works
offling. We can punt on offline log message templates, but we can't
really punt on offline ignores values or (probably) auto-props or ttb
values.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 9 06:51:21 2005