Re: Log message templates revisited.

Michael Sweet wrote:
> kfogel@collab.net wrote:
>> ...
>> If we can think of a robust way to implement inherited properties, I'm
>> all for solving log message templates and everything else that way.
>> But is such a solution really available? (An existence proof would be
>> best :-). )
>
> Call me dense, but wouldn't this "walk up" method for log templates
> also work for inherited properties?
>

Yeah, but the difference is that the log templates are needed at only
one narrowly defined time (commit), whereas the inherited properties may
be needed at several places (add, revert, etc). It may be acceptable to
require a network access to retrieve the log template from the
repository, but I doubt that would be acceptable for generic iprops.

Storing inherited properties (whether they be log templates or not) in
each admin directory of a WC cause the least amount of change in the
existing WC code, but causes edge cases (as we keep going round and
round on it). I've come to like the lazy populate idea that GHudson
proposed, but I'd like to know what problems KFogel had with that.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org