Ryan and Garrett have since explained to me that I, again, largely
confused. While 'svn log filename' does indeed display logging
information, mixed revisions is what is causing my misunderstanding of
"svn log".
After running 'svn up' as suggested, 'svn log' displays _precisely_ what I
expected it to do so in the first place.
A small gotcha, and one I shouldn't have been gotten by since I did read
the daffy book to help me set the software up in the first place.
Again, all, thank you for your help in solving my problems.
I do have to say, this is the most useful users list I've ever subscribed
to. Usually when someone asks a dumb question like mine, they get ignored.
Well done to you.
JP
On 22 Dec 2005 kfogel@collab.net wrote:
> JP Hindin <jplist@kiwigeek.com> writes:
> > My mistake was assuming that an "svn log" in a specific directory would
> > like the logs for all changes in that directory. It appears, however, that
> > one must supply a specific file (or files) to do the log function on.
>
> That's not quite the problem. The problem is rather that "svn log"
> takes "." as its implied target. Since "." has a revision number, svn
> only shows logs from 1 to that revision number. If you update ".",
> *or* pass the -rHEAD option to svn, you may see more logs.
>
> -Karl
>
> --
> www.collab.net <> CollabNet | Distributed Development On Demand
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Dec 25 04:12:04 2005