[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r13754 - trunk/contrib/client-side

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2005-03-30 17:21:46 CEST

Philip Martin <philip@codematters.co.uk> writes:

> Simon Perreault <nomis80@nomis80.org> writes:
> > On March 29, 2005 18:48, Philip Martin wrote:
> >> Please follow the project log message guidelines in the HACKING file,
> >> something like:
> >>
> >> * contrib/client-side/svn-clean (blah): blah blah blah
> >
> > Sorry, I thought I was following the instructions in the HACKING file:
> >
> > * If your change was only to one file, or was the same change to
> > multiple files, then there's no need to list their paths in the
> > log message (because "svn log" can show the changed paths for
> > that revision anyway). Only when you need to describe how the
> > change affected different areas in different ways is it
> > necessary to organize the log message by paths and symbols, as
> > in the examples above.
> Hmm, if I run 'svn log' on my working copy I get your log message, and
> even though it applies to only one file I don't know which file that
> it. The rule you quote only makes sense if I'm running 'svn log' on
> the file in question, but that's not the common case.

I think you're reading the HACKING paragraph too literally. I'm
betting that the specific command 'svn log -v' is what the HACKING
author had in mind when he mentioned the generic operation "svn log".

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 30 18:09:54 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.