Hmm. I've done quite a few commits without a filename, where the commit
affected just a single file. Generally, I see the need for multiple files in
the message as a way to say what you did to each file. When the commit
involves just a single file... well, the log message says what happened. No
need for further refinement.
IOW, I find Jim's commit message to be quite fine. *Especially* given that
it is the commit which introduced the file in the first place.
Now if you want to bring up something about "searching log messages for a
filename", then I'm going to have to respond by whapping you with my big ol'
Cluestick(tm). :-)
Cheers,
-g
On Mon, Jul 15, 2002 at 08:42:36PM -0500, Karl Fogel wrote:
> jimb@tigris.org writes:
> > New Revision: 2537
> >
> > Added:
> > trunk/tools/client-side/vc-svn.el
> > Log:
> > Add preliminary code for a Subversion back end for the Emacs `VC' package.
>
> Yay!
>
> Up till now, we've been consistent about following the
>
> "* filename: log message"
>
> format, but that's less important now that "svn log" is about to be
> able to show changed paths efficiently. If there were more than one
> path affected by the commit, that would be different, but here the
> meaning is unambiguous. So I don't think this msg needs to be
> changed.
>
> However, Jim, in case you ever need to fix a typo in a log message
> after commit, the URL is:
>
> http://svn.collab.net/scripts/tweak-log.cgi
>
> -Karl
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
--
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 16 10:03:08 2002