Karl Fogel <kfogel@newton.ch.collab.net> writes:
> Oh, if *that's* the problem, then there's no problem.
>
> $ svn log -v
Maybe. I suppose the "Changed paths" line is what you were talking
about. It doesn't look like what i want, but i suppose i'll give
it a try. Why is this information withheld without -v? It's only
an extra line, not verbose output i'd expect to be hidden behind
-v.
> The fix is not yet installed on the Subversion server, since we
> haven't upgraded our repository, but it will be soon. If you're
> running your own repository, then it just depends, of course.
Yeah, it works great.
> Hmm, that's a problem. If you have a patch for the help output, that
> would be great.
How about this?
Display the log messages for local PATHs or PATHs at the URL.
If URL is given by itself, then log messages are output for
that specific path. The log messages for each file are all
collected, sorted, and output in order without regard to which
PATH the log message came from. The -v option will include a
list of affected files for each log message.. By default, the
resultant collection of log messages for a given path will
include logs for all the revisions in which that path's node
was modified, spanning copy history where such exists. This
can be disabled by using the --strict option. Examples are:
While i'm here, what does --strict do? Is it just --dont-follow-copies
like that description sounds like? If so, its description a few
lines later ("use strict semantics") is not very good. What "strict
semantics" are is not obvious.
--
Eric Gillespie <*> epg@pretzelnet.org
Build a fire for a man, and he'll be warm for a day. Set a man on
fire, and he'll be warm for the rest of his life. -Terry Pratchett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jul 21 08:40:23 2002