Re: Enhancement request for the merging API: "Commit message suggestion"

On Tuesday 06 November 2007 20:26:38 David Glasser wrote:

> While backwards compatibility is generally a good idea, I don't see
> why we should actively add a feature that we instantly deprecate
> against current servers. There's a difference between preserving old
> behaviors and adding new ones.

Thanks for your comments.

OK, you convinced me not implementing "Commit message suggestion " is the
better solution in the long term. Until all clients and servers have both
updated to 1.5 phrasing good log messages is going to be cumbersome though.

In a perfect world (SVN 1.5 Client, SVN 1.5 Server) what would a good log
message look like when merging? The log message could stay empty in most
cases since the information provided there can be optained bei 'svn -g'.

'svn -g' currently doesn't show the original parameters of the merge: was
accestory ignored, were line endings ignored, were whitespace changes
ignored, which conflicts occured, which targets were skipped during the
merge, (possibly more...).
This could be part of the suggested log message, although it could also be
stored as metadata somewhere else.

IMHO, a sensible suggestion (summary) would ease merging with the
combination SVN 1.5 client/1.4.x or 1.3.x server. It's going to take a while
for all servers to update to 1.5.
http://tortoisesvn.tigris.org/svn/tortoisesvn/ ist currently still using
1.3.1 :-(

Tobias

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org