Chris Pepper wrote:
> This is neat, but since I'm working with docs instead of functions,
> svnlog doesn't seem to get me anything more than "svn diff | bbedit",
> which I've been using. I'd like something to dump it into the log
> template, to save me a step.
>
> I think what I really want would be a second loop in util.c, after
> the list of files with status has been generated. If a (new) flag was
> set, svn would loop across the files to be committed again, appending a
> diff for each one on this round. It would be cleaned out of the actual
> log message automatically, same as the current list of files is ignored.
>
> Would anyone else find this useful??
I'm sure some people would find it of some utility, but the trouble is
that the more "svn" tries to write your log message for you, the less
people it will satisfy - either that, or it grows lots of options and
configurability and becomes a generic log message writer trying to suit
everybody.
I don't think that Subversion should head in that direction. (I don't
even think it should invoke an editor for you, but I seem to be in the
minority there.) I recommend writing an external log-message-generator
that suits your purposes, and put its name in the SVN_EDITOR environment
variable so that Subversion calls it instead of a plain editor.
If the log message utility that you write is neat and tidy and useful to
lots of people, we could then include it as a tool in the Subversion
distribution.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 14 16:21:32 2004