> From: kfogel@collab.net <kfogel@collab.net>
> Date: 02 Sep 2003 13:59:44 -0500
> Content-Type: text/plain; charset=us-ascii
> Subject: How does log translate to diff
>
>
> Jack Repenning <jrepenning@collab.net> writes:
> > >I'd interpret this to mean that one line changed between these two
> > >revisions.
> >
> > I think the "1 line" thing is just bogus. I always seem to get that
> > claim, no matter how much change has occurred.
>
> It gives the number of lines in the log message, not the number of
> lines in the change. (It's to help auto-parsing of the log message.)
Does anyone here actually think it is more important to inform
auto-parsers of the number of lines in the log message (which could
surely be determined anyway by just counting newline characters or
whatever, and for that matter autoparser tools probably just reformat
the log entry themselves) than to inform human readers of how many
lines were changed?
However, note that, in fact, it CANNOT be lines changed, since the log
entries are for _changesets_, not indidivual files. However the other
surface parallels to CVS log messages make this very confusing to CVS
users -- most probably assume the tool is just broken ("the 1 lines is
bogus" as people have been saying).
I therefore suggest removing the "XX lines" info completely (not really
useful, and confusing to new adopters, particularly since it doesn't
seem to be documented anywhere), and adding the traditional CVS "+x-y"
info to the "svn log -v" output (put it next to each item under
"Changed paths:". This +/- info really is very useful -- it tells at a
glance "how much change" occurred in the file, AND whether the code
grew larger or smaller in the change (a very useful piece of
information for developers).
Anyone agree or disagree?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 9 18:32:58 2004