Re: RFC: Log Message Templates via new hook.

Julian Foad wrote:
> What does this mean for TortoiseSVN? Taking the Subversion project's
> log message style as an example again (other real-world examples
> welcome), we see now that while TSVN is generating the file list, the
> user could be writing the log message introduction and general
> description. Then the file list should be inserted, and then the user
> can go on writing the detailed part of the log message.

I think this is a workable compromise (but of course I don't use TSVN, so don't
take that as anything more than what it is).

> Further, I would say that the file list really must be automatically
> formatted in the project's chosen style. If it were presented always in
> a built-in fixed style, then it would not really be very useful in
> providing a starting point for the user's text, and would only really be
> a reminder.

One thing that occurred to me earlier was that while $Files$ could be used as a
substitution for the entire listing of files to be committed (using some default
format), $File$ could be used as an iterative loop with custom formatting. So
for example, the Subversion project template could have the following line:

   * $File$:

which would be expanded to a series of lines containing one file per line (with
a blank line in between?).

However, the problem with this scheme is that either every client would have to
implement this substitution scheme or the client library would have to export a
trivial formatting function which would just take a list of filenames and return
a block of text. Actually, the latter isn't such a bad thing since the client
code could determine the appropriate relative path (highest common repository
path among all of the committed files?) to display.

NOTE: that nothing here precludes either the server hook or the iprop scheme.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org