Re: RFC: Log Message Templates via new hook.

Mark Phippard wrote:
> I was just assuming that iprops would be implemented as "normal" props
> except that there would be something to trigger the inherited behavior. If
> this were the case, then building a log message template solution around
> properties would continue to "just work" with iprops, it is just that the
> props would be easier for the user to set.

That's basically what I was going to suggest:

Phase 1 - make files inherit all iprops from their containing directory as
ordinary props. Reuse that to enable the code that creates the logs to check
for the special svn:log-template property (which is just a special case iprop)
in the target's directory.

Phase 2 - handle the inheritance issues - the more I think about it, the more
drawn I am to Greg Hudson's proposal as a much more practical and easier to
specify scheme than the more elaborate in-tree inheritance.

Phase 1 could be added to 1.3 and phase 2 could be added later or at the same
time depending on difficulty. People could start using phase 1 immediately by
just manually setting the iprop in the tree (which is how they are going to have
to bootstrap existing trees anyways).

The nice thing about going this route is that if we get some fabulous ACL scheme
which also lends itself to in-tree inheritance, we could just add that as
another way for the Phase 1 code to gain access to the properties it is
interested in.

John

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