[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn log hides log messages

From: Christopher Ness <chris_at_nesser.org>
Date: 2005-01-04 20:42:01 CET

On Wed, 2004-29-12 at 13:39 -0600, erh@swapsimple.com wrote:
> On Wed, Dec 29, 2004 at 03:21:37AM -0500, Jim Correia wrote:
> > On Dec 27, 2004, at 7:24 PM, erh@swapsimple.com wrote:
> > > "svn log" has really annoying behaviour where is hides log messages
> > >for revisions that are newer than what is currently checked out. I
> > >read
> > >a few messages that mentions this, and it seems that this won't be
> > >changing
> > >any time soon, but I find this behaviour horribly confusing.

8< snip 8<

> > svn log -r HEAD:0 file.ext
>
> oh, yeah, of course.
> hmm... I guess I'll just write a wrapper script to add the
> default. ugh.

Well, it doesn't take much to realize that some commands take place on
the server, and some on the working copy.

Perhaps a solution would be to update the information for committed
files ONLY in the working copy. This would be very fast without network
communication to the server.

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.

Make sense? Or am I just blowing steam?
Cheers,
Chris

-- 
Software Engineering IV,
McMaster University
PGP Public Key: http://www.nesser.org/pgp-key/
14:31:59 up 1 day, 16:15, 2 users, load average: 0.23, 0.28, 0.31 
http://www.fsf.org/philosophy/no-word-attachments.html

Received on Tue Jan 4 20:44:30 2005

This is an archived mail posted to the Subversion Users mailing list.