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

[PATCH] Correctly handle SVN_INVALID_REVNUM in svn_repos_get_logs4 even for start < head

From: David Glasser <glasser_at_davidglasser.net>
Date: Tue, 14 Oct 2008 14:28:43 -0700

I'd run tests and commit, but apparently we now require a newer
sqlite3 than my work machine has installed, and while I recognize that
sqlite3 is really really easy to build, it's still more activation
energy than I have today. Sorry.

[[[
* subversion/libsvn_repos/log.c
  (svn_repos_get_logs4): For the ascending-revisions case, handle
SVN_INVALID_REVNUM
   arguments correctly.
]]]

Index: subversion/libsvn_repos/log.c
===================================================================
--- subversion/libsvn_repos/log.c (revision 33643)
+++ subversion/libsvn_repos/log.c (working copy)
@@ -1612,10 +1612,10 @@
   SVN_ERR(svn_fs_youngest_rev(&head, fs, pool));

   if (! SVN_IS_VALID_REVNUM(start))
- start = head;
+ hist_start = start = head;

   if (! SVN_IS_VALID_REVNUM(end))
- end = head;
+ hist_end = end = head;

   /* Check that revisions are sane before ever invoking receiver. */
   if (start > head)

-- 
David Glasser | glasser@davidglasser.net | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-14 23:29:00 CEST

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