Dmitry Batrak <[email protected]> writes: > The following command: > > svn log > https://svn.apache.org/repos/asf/subversion/branches/gnome-keyring/subversion/bindings/javahl@871338 > -r 870558:871338 -g > > returns a number of irrelevant revisions (in particular, 870728, > 870496, 869828) in the 'main' line of the log, i.e. not as merged > revisions (full command output is attached). > Neither of the below commands return those revisions in the 'main' line: > > svn log > https://svn.apache.org/repos/asf/subversion/branches/gnome-keyring/subversion/bindings/javahl@871338 > -r 870558:871338 > > svn log > https://svn.apache.org/repos/asf/subversion/branches/gnome-keyring/subversion/bindings/javahl@871338 > -r 871338:870558 -g > > I think this is a server-side problem (server seems to use 1.7.0 SVN > version), but, just in case, I'm using SlikSvn-1.7.1-WIN32 client. > > Is this a known bug, or should I raise an issue in the issue tracker for it?
Yes, that does look like a bug. Please raise an issue. -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com
