[Fwd: [WWW PATCH] Re: svn log hides log messages]

Ben asked me to send this patch to the FAQ page to the dev list. I'm
not a member of dev, if something is wrong or needs rework please copy
me.

Thanks,
Chris

-------- Forwarded Message --------
> From: Christopher Ness <chris@nesser.org>
> To: Ben Collins-Sussman <sussman@collab.net>
> Subject: [WWW PATCH] Re: svn log hides log messages
> Date: Wed, 05 Jan 2005 01:02:17 -0500
> On Tue, 2005-04-01 at 18:33 -0600, Ben Collins-Sussman wrote:
> > (Everytime I explain this on the list, I swear under my breath that
> > there's no FAQ for this in the book or website. But now there's a
> > possibility the behavior may change, so I'm not going to write the FAQ.
> > Instead, I'm going to repeat it all again, because I'm too lazy to
> > look up my last explanation in the mail archives. :-) )
> >
> > If you have a working copy at r5, then 'svn commit foo.c', then foo.c
> > is at r6, everything else still at r5. We've already established that.
> >
> > When you run 'svn log' with no arguments, it assumes a target of '.'
> > just like every other command -- that is, that the 'target' of the
> > command is the parent directory of foo.c. You're asking the server to
> > "tell me all commits that ever happened to (or within) the parent
> > directory." And because no peg-revision was specified, it assumes you
> > want to know all commits that ever affected the parent directory *at
> > its base revision*, which is 5. So the server happily digs up
> > revision 5 of the parent directory, and starts searching backwards
> > through commits: r5, r4, r3, r2... and so on, sending only commit logs
> > that affected that directory.
> >
> > If you had run 'svn update' first, to bring the entire working copy to
> > r6, then 'svn log' would ask for the history of '.' at r6, and
> > therefore you would see the commit you just made to foo.c.
>
> Hope I captured the nature of the beast above in this patch. Not sure
> the best way to send it in so I just took a diff.
>
> -m "Added FAQ: I cannot see the log entry for the file I just committed,
> why? Sussman explained it on the mailing list, I made some HTML"
>
> Cheers,
> Chris

-- 
Software Engineering IV,
McMaster University
PGP Public Key: http://www.nesser.org/pgp-key/
10:43:49 up 2 days, 12:27, 2 users, load average: 0.00, 0.01, 0.00 
http://www.fsf.org/philosophy/no-word-attachments.html