Re: RFC: Log Message Templates via new hook.

John Peacock <jpeacock@rowman.com> writes:

> Here's a couple of ideas for dealing with conflicts (straight from my
> brain to your eyes, no thought to complexity of implementation):
>
> 1) Highest One Wins - the template in force for the shortest path that
> contains all committed file paths.

This is sane, and can be implemented off the bat by simply having
svn_ra_get_commit_editor() return the log message template of the
session URL which is used as the anchor of the commit.

> 2) To Each His Own - If those 20 files are covered by 3 log-templates
> (for example), then the client splits the commit into 3 seperate
> commits, each with it's own custom template. We should be able to
> assume that if a site has that many templates scattered about their
> tree, then that should be taken as a significant factor and we should
> respect the effort and not impose a single template.

This is *not* sane. Atomicity of commits is one of our super-clear
wins over CVS. Let's never forsake that, please.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 19 18:33:54 2005