Re: "svn log" behavior and implementation

Yoshiki Hayashi <yoshiki@xemacs.org> writes:
> > $ svn log -r 20:30 foo.c
>
> Just to be sure, what will be the output of this command?
> It will show log message which foo.c was changed, right?

Right. All revisions from 20-30 inclusive in which foo.c was changed.
If foo.c wasn't changed in any of those revisions, then there will be
no output (or no log messages, anyway).

> > Each commit's log message contains the revision number, author, date,
> > and the actual log comment. Should each message also contain all the
> > changed paths for that commit? (That is, all files on which text or
> > props have been changed, and all dirs on which props have been changed
> > or entries added or deleted.)
>
> If that functionality is desired, I want them to be a
> separate command or add an option to show changed files.
> It probably depends on the way the log is written but I
> normally don't want every changed files to be listed by
> typing svn log.

So to summarize the current feedback:

   Yoshiki favors not showing changed files by default.

   Sander Striker favors not showing them *when log was invoked on
   specific files* (i.e., if one asked about foo.c, then the output
   doesn't need to show whether bar.c was changed in some of those
   same commits).

   Karl favors showing all changed files every time, whether one ran
   "svn log" on particular arguments or not.

Sigh. I think we need some more feedback. :-)

In the meantime, I'll make sure there are hooks in the implementation
to go either way.

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:45 2006