On Fri, 2008-11-07 at 00:09 +0100, Neels J. Hofmeyr wrote:
>
> Julian Foad wrote:
> > On Wed, 2008-11-05 at 12:10 -0800, Greg Stein wrote:
> >> Seriously... are we going to have to install a pre-commit hook to fail
> >> if people keep inserting diffs into the log message?
> >
> > Maybe it's only me that keeps inserting diffs in the log message. I'll
> > keep an eye open for ways to change my working practices to avoid this,
> > but I can't see it's very likely at this point. At the moment I normally
> > keep patches (with log message and diff) until ready to commit, and then
> > try to remember to delete the diff and use the file as the log message
> > with "svn ci -F/--file FILE".
>
> Hm, I just keep a separate "log" file in each working copy root. It's handy
> for me to have two separate vims open on the diff and the log message, much
> easier copy-pasting of file/function names via Shift-middle-mouse-button.
>
> Has someone actually come up with a script to automatically print a log
> message skeleton with all files and function names in it? Would be nice to
> save us that copy-paste orgy each time we commit.
Yes: attached is my "svnlogmsg" script. It prints a log message
skeleton, plus a diff, to stdout. I use it like this:
[[[
svnlogmsg > ff
vim ff # I edit the message, and delete the diff
svn ci -F ff && rm ff
]]]
or, another example, from within Vim:
[[[
# make a new file and read in a log skeleton:
:e ff
:r !svnlogmsg subversion/include/
# edit the text and delete the diff
# ...
# commit from within Vim
:!svn ci -F ff && rm ff
]]]
Hope it's useful or inspiring.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
- application/x-shellscript attachment: stored
Received on 2008-11-07 00:48:12 CET