Re: svn log hides log messages

On Tue, 2005-04-01 at 14:13 -0600, Ben Collins-Sussman wrote:
> On Jan 4, 2005, at 1:42 PM, Christopher Ness wrote:
> >
> > For example:
> > `svn commit ./Makefile -m "Added new target: clean"`
> >
> > Ends up modifying the data in .svn (the working copy) to update only
> > the
> > entr{y,ies} for files affected by the commit. Therefore you now have
> > the data in the working copy about the recent commit, but no new
> > information is available about files which have not been committed.
> > You
> > still have a mixed working copy but you have information in your
> > working
> > copy about your last commit.
>
> This is already how 'svn commit' works.
>
> If your working copy is all at r5, and 'svn commit' discovers and
> commits foo.c, then after the commit:
>
> foo.c is at r6
> the whole rest of the working copy is at r5
>
> In other words, you have a mixed-rev working copy after *every* commit.
> Only 'svn update' brings the whole working copy to the same revision.

I don't know how the working copy stores information. I'll admit that
right now so I may have some misplaced ideas.

`status -v` knows that foo.c is at r6 and the rest of the working copy
is at r5 after the commit you described.

My question is this: Is the log information [and other metadata] for
(foo.c@r6) available in the working copy data structures after the
commit?

I assumed [ass outta you and me] the reason the `log` command held back
the new revision info was that the working copy didn't have the required
metadata until and `update` command was issued.

Chris

-- 
Software Engineering IV,
McMaster University
PGP Public Key: http://www.nesser.org/pgp-key/
16:45:43 up 1 day, 18:29, 3 users, load average: 0.27, 0.08, 0.02 
http://www.fsf.org/philosophy/no-word-attachments.html