On 11/5/07, David Glasser <glasser@davidglasser.net> wrote:
> On 11/5/07, Tobias Schäfer <tobiasschaefer@gmx.de> wrote:
> > Hi devs,
> >
> > I have a enhancement request for the merging API.
> >
> > Problem 1:
> > Whenever a revision is merged TortoiseSVN 1.5.0-dev suggests a commit
> > message based on the revisions which have been merged and their author and
> > commit message ("Commit message suggestions"). Unfortunately it cannot tell
> > if a revision specified by the user was really merged. For example a
> > revision could have been blocked by an existing svn:mergeinfo entry.
> > Therefore the created log message sometimes contains too many entries.
> >
> > Problem 2:
> > A further problem is that every SVN client might generate this commit
> > message in a slightly different way.
> >
> > The solution to both problems:
> > Could the callback of svn_client_merge_peg4 (notify_func of
> > svn_client_ctx_t) please provide a suggested commit message at the end of
> > the merge. All SVN clients will then be able to present this to the user so
> > that he can use it.
> > This log message should be formated similar to the one svnmerge.py creates,
> > maybe even exactly the same format.
>
> Given the existence of 'svn log -g', should we really be encouraging
> log messages that include the logs of the merged revisions? (The
> header summary line is very useful of course.)
I agree with you David. The solution is to discourage people from
using the commit message in this manner. The svn log -g support is
superior and it just reinforces that you do not need to use the log
message for this sort of book keeping any more.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 5 20:44:39 2007