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

RFC: svn update --print-log-messages

From: mark benedetto king <bking_at_answerfriend.com>
Date: 2002-12-16 17:34:51 CET

This kind of thing happens to me quite a bit:

$ svn up
U notes/autoversioning-strategy.txt
Updated to revision 1234.

When I see that, I think to myself "hey, I wonder what spiffy updates
happened there?"

But it's too late for me to find out, isn't it? I don't know my last
version anymore.

svn diff -rPREV:COMMITTED notes/autoversioning-strategy.txt

is nice, but doesn't cut it. That tells me the last commit. But
there might have been several commits rolled into the update that
I received.

Now, I recognize that keeping a "revisions I've seen" history in the
WC is probably overkill. But what if there were an option to update
to print the log messages of the updates in order?

$ svn up --print-log-messages
rev 3987: sussman | 2002-12-04 10:55:07 -0500 (Wed, 04 Dec 2002) | 8 lines

Time to make the doughnuts^H^H^H^H^H^H^H^H^H^H^H^H release svn.

* svn_version.h (SVN_VER_MINOR): bump to 0.16

* CHANGES: update with changes from r3928:3985, set date and revnum.

* tarball_release_procedure.txt: mention posting of latest docs.
rev 4053: philip | 2002-12-08 08:00:37 -0500 (Sun, 08 Dec 2002) | 10 lines

Fix issue 1029, make working-copy to repository copies work.

* subversion/libsvn_client/copy.c (wc_to_repos_copy): Use absolute path
  to open access baton. Use correct directory access baton when getting
  committables. Tweak flags used to open the base URLra session.

* subversion/tests/clients/cmdline/copy_tests.py (wc_to_repos): New test

* CHANGES: State that this now works.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 16 17:44:15 2002

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