Re: [VOTE] merge the log-message-templates branch to trunk
On Mon, Sep 15, 2014 at 03:37:22PM -0700, Alexey Neyman wrote:
> On Monday, September 15, 2014 10:25:42 AM Julian Foad wrote:
> ... snip ...
> > Instead of a 'get_log_message(list_of_commit_items)' we should have
> > 'get_rev_props_for_commit(list_of_commit_items)', and instead of a template
> > we should have:
> > - a list of required and optional rev-props (usually including svn:log);
> > - a template for each;
> > - a help message for each.
> > > And perhaps we could introduce a template syntax to specify
> > > key-value pairs (e.g. "%KEYWORD:%") which are removed automatically
> > > if the value is left empty?
> Will it be possible to translate these keywords to actual revision properties? E.g.
> something like having %foo:bar%Foo:% in the template, and if "Foo:" value is non-empty,
> have a foo:bar property set on the committed revision?
My biggest concern with this is that people could edit their log messages
changing these fields but forget to sync up the corresponding revprops.
Received on 2014-09-16 10:14:24 CEST
This is an archived mail posted to the Subversion Dev