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

Re: svn update and log

From: Mark <cm_mark_at_yahoo.com>
Date: 2002-04-28 03:32:14 CEST

I may not have been clear on what I was trying to achieve. If I perform an
update on any directory in the svn workarea (not necessarily from the top), it
displays the files that are updated in the workarea. This is the same as in

My primary interest in that situation is what are those changes that where just
brought into my workarea. With CVS, I had to run a 'cvs stat' then a 'cvs log
-N -r<rev>' for each file to get a basic view of what I just pulled into my
workarea, by reading the commit message to get a basic understanding of what
fixes of functionality changes that where updated into my workarea. I am not
interested in the full log history of each file, or even a log for a revision
of a file, in subversion I am intested in the commit log of just the commits
that where updated into my workarea.

That two step process for each updated file was less than ideal. With checkins
in subversion being atomic, I was looking for a way to reduce the steps in the
above cvs process and take advantage of the commits being atomic.

Is there a better way to do this? How do people normally find out about changes
brought into their workarea? Maybe there is a better way to go about what I am
trying to do.

I was suggesting that svn update be able to list the commit numbers updated to
the workarea, for each file updated in the workarea, maybe a --verbose option.

Maybe the suggestion svn log option for the log message of the current version
isn't all that helpful. Maybe giving an svn log -r<rev> command without a
filename could provide a list of the files modified with the commit, plus the
log message and other commit info, that might be helpful.

Anyway, thanks for responding. It looks like what I do after updates isn't all
that common.


--- Karl Fogel <kfogel@newton.ch.collab.net> wrote:
> Mark <cm_mark@yahoo.com> writes:
> > Would it be good to have the version number be added to the update line? I
> > think the info is availble during the update (for the .svn dir), maybe
> stick
> > the number on the end of each line on the output.
> IMHO, the per-file update lines are crowded enough as it is, and we
> don't want to lose path space to new information.
> > Also, with svn log, would it be possible to add an option to display log
> > (comment) info on the current version of the file in the workarea (whatever
> > version that is), maybe
> > > svn log -c file.c
> Why would the most recent log message be more interesting than the
> ones before it? That log message doesn't apply to "the current
> version of the file", it applies to a particular change. The current
> version therefore has *lots* of log messages associated with it, and
> we can't store them all locally.
> -K
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org

Do You Yahoo!?
Yahoo! Health - your guide to health and wellness

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 28 03:33:24 2002

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