Julian Foad wrote:
> 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
> ]]]
Wow, Julian, that's so awesome!
I did find some peculiar behaviour (attached) when changing the very first
line of a function (which "trickles" down consecutive changes), or when
changing a function name. Fair enough, I read the diffs anyway.
It's not completely 100% reliable, but it's really really close, considering
that real-world changes will almost certainly show all the correct function
names (and maybe some more). What a great help this will be! Thanks a lot!
~Neels
* subversion/libsvn_ra/ra_loader.c
(check_ra_version):
Index: subversion/libsvn_ra/ra_loader.c
===================================================================
--- subversion/libsvn_ra/ra_loader.c (revision 34112)
+++ subversion/libsvn_ra/ra_loader.c (working copy)
@@ -244,8 +244,11 @@ check_ra_version(const svn_version_t *ra
/*** Public Interfaces ***/
-svn_error_t *svn_ra_initialize(apr_pool_t *pool)
-{
+svn_error_t *svn_ra_initialize(apr_pool_t *pool, foo)
+{ change
+ change change change
+ change change change
+ change change change
return SVN_NO_ERROR;
}
@@ -258,7 +261,7 @@ svn_error_t *svn_ra_initialize(apr_pool_
* code in wrapper_template.h:compat_open() in sync with your
* changes. */
svn_error_t *
-svn_ra_create_callbacks(svn_ra_callbacks2_t **callbacks,
+new_name(svn_ra_callbacks2_t **callbacks,
apr_pool_t *pool)
{
*callbacks = apr_pcalloc(pool, sizeof(**callbacks));
Received on 2008-11-09 02:21:02 CET