svn log -g doesn't return merge info when operating against repository root

Hello. The command "svn log -vg" is not returning merge info when I execute the command while sitting in a working copy of the root level of a repository or when I pass in the URL to the root level of root level on the command line. A simple test case can be seen below. I see there is already an

Re: predecessor count for the root node-revision is wrong message

On Thu, Mar 22, 2012 at 1:13 PM, Daniel Shahaf wrote: > Justin Johnson wrote on Thu, Mar 22, 2012 at 13:03:04 -0500: > > On Tue, Mar 20, 2012 at 2:32 PM, Daniel Shahaf > wrote: > > > > > Daniel Shahaf wrote on Tue, Mar 20, 2012 at 00:49:06 +0200: > > > > T

Re: predecessor count for the root node-revision is wrong message

On Tue, Mar 20, 2012 at 2:32 PM, Daniel Shahaf wrote: > Daniel Shahaf wrote on Tue, Mar 20, 2012 at 00:49:06 +0200: > > The time until 1.7.5 is counted in weeks, and 1.6.18 is scheduled to be > > released next week. > > > > The fix was merged to 1.6.x@HEAD today and barring surprises will be > in

Re: predecessor count for the root node-revision is wrong message

On Fri, Mar 2, 2012 at 6:21 AM, Daniel Shahaf wrote: > Daniel Shahaf wrote on Fri, Mar 02, 2012 at 12:21:46 +0200: > > Daniel Shahaf wrote on Wed, Feb 29, 2012 at 18:15:41 +0200: > > > Justin, Jason, > > > > > > Some things you could do are: > > > > > > - What RA method do you use? svn:// or htt

Re: predecessor count for the root node-revision is wrong message

On Fri, Mar 2, 2012 at 3:41 AM, Daniel Shahaf wrote: > Justin Johnson wrote on Thu, Mar 01, 2012 at 07:45:08 -0600: > > On Wed, Feb 29, 2012 at 4:14 PM, Justin Johnson < > justinandto...@gmail.com>wrote: > > > On Wed, Feb 29, 2012 at 11:22 AM, Daniel Shahaf > w

Re: predecessor count for the root node-revision is wrong message

> > > > > > - Are the failing revisions always small (eg: just a URL-URL copy), >>> > > > > or always large (eg: results of a merge)? >>> > > > > >>> > > > > >>> > > > As mentioned before, so far it appears to be 1) create a tag by >>> copying >>> > > an >>> > > > entire working copy of a branch t

Re: predecessor count for the root node-revision is wrong message

On Wed, Feb 29, 2012 at 4:14 PM, Justin Johnson wrote: > On Wed, Feb 29, 2012 at 11:22 AM, Daniel Shahaf wrote: > >> Justin Johnson wrote on Wed, Feb 29, 2012 at 11:11:18 -0600: >> > On Wed, Feb 29, 2012 at 10:35 AM, Daniel Shahaf >> wrote: >> > >> >

Re: predecessor count for the root node-revision is wrong message

On Wed, Feb 29, 2012 at 11:22 AM, Daniel Shahaf wrote: > Justin Johnson wrote on Wed, Feb 29, 2012 at 11:11:18 -0600: > > On Wed, Feb 29, 2012 at 10:35 AM, Daniel Shahaf > wrote: > > > > > Justin Johnson wrote on Wed, Feb 29, 2012 at 10:25:38 -0600: > > >

Re: predecessor count for the root node-revision is wrong message

On Wed, Feb 29, 2012 at 10:35 AM, Daniel Shahaf wrote: > Justin Johnson wrote on Wed, Feb 29, 2012 at 10:25:38 -0600: > > On Wed, Feb 29, 2012 at 10:15 AM, Daniel Shahaf > wrote: > > > - Are the failing revisions always small (eg: just a URL-URL copy), > > > or

Re: predecessor count for the root node-revision is wrong message

I've asked Jason upthread some > questions (eg, whether there patterns of commits concurrent to the > failing ones), which likely apply to you too. > > Daniel > > Justin Johnson wrote on Wed, Feb 29, 2012 at 09:22:40 -0600: > > On Tue, Feb 28, 2012 at 3:07 AM, Daniel Shaha

Re: predecessor count for the root node-revision is wrong message

On Tue, Feb 28, 2012 at 3:07 AM, Daniel Shahaf wrote: > Jason Wong wrote on Mon, Feb 27, 2012 at 07:36:39 -0800: > > On Thu, Feb 16, 2012 at 12:14 PM, Daniel Shahaf > wrote: > > > > > > > > The output from these two tells me two things: > > > > > > 1. The minfo-cnt value is reasonable (within a

Re: svn status returns incorrect results on Windows 7

On Tue, Jan 31, 2012 at 2:47 AM, Johan Corveleyn wrote: > On Tue, Jan 31, 2012 at 3:35 AM, Justin Johnson > wrote: >> On Sun, Jan 29, 2012 at 3:25 PM, Konstantin Kolinko >> wrote: >>> 2012/1/27 Justin Johnson : >>>> Hi, >>>> >>>> I

Re: svn status returns incorrect results on Windows 7

On Sun, Jan 29, 2012 at 3:25 PM, Konstantin Kolinko wrote: > 2012/1/27 Justin Johnson : >> Hi, >> >> I am running Subversion 1.7.2 64 bit installer from CollabNet on >> Windows 7.  The problem I'm experiencing can be seen in the output >> below.  In summ

Re: Could not read chunk size: connection was closed by server

On Wed, Nov 23, 2011 at 11:46 AM, Justin Johnson wrote: >> >>> during a checkout. >>> >>>   Could not read chunk size: connection was closed by server >>> >>> In the server logs the following errors appear around the same time. >>>

svn status returns incorrect results on Windows 7

Hi, I am running Subversion 1.7.2 64 bit installer from CollabNet on Windows 7. The problem I'm experiencing can be seen in the output below. In summary, svn status is returning incorrect results, sometimes not showing that something has been modified and sometimes not recognizing that I'm in a

Re: Could not read chunk size: connection was closed by server

> >> during a checkout. >> >>   Could not read chunk size: connection was closed by server >> >> In the server logs the following errors appear around the same time. >> >>   Provider encountered an error while streaming a REPORT response.  [500, #0] >>   A failure occurred while driving the update

Re: Could not read chunk size: connection was closed by server

On Fri, Nov 18, 2011 at 3:27 PM, Justin Johnson wrote: > Hi, > > We are running Subversion 1.6.16 and Apache 2.2.17 on Solaris 10, with > 1.6.12 clients connecting from Windows and various flavors of UNIX. > For as long as I can remember users on Windows and UNIX clients have >

Could not read chunk size: connection was closed by server

Hi, We are running Subversion 1.6.16 and Apache 2.2.17 on Solaris 10, with 1.6.12 clients connecting from Windows and various flavors of UNIX. For as long as I can remember users on Windows and UNIX clients have been getting the following error every once in a while, typically during a checkout.

Re: auto-props on import use local temp file name instead of remote destination file name

> > Hi Justin, > > On Fri, Jun 25, 2010 at 09:09:39AM -0500, Justin Johnson wrote: > > > I am attempting to import a file and set svn:eol-style in one command > using > > the --auto-props and --config-option options to svn import. When I do > the > > impor

Re: auto-props on import use local temp file name instead of remote destination file name

> > Hi, > > I am attempting to import a file and set svn:eol-style in one command using > the --auto-props and --config-option options to svn import. When I do the > import I explicitly specify the file name in the import URL. The reason I > do this is because I want to import from a randomly gen

auto-props on import use local temp file name instead of remote destination file name

Hi, I am attempting to import a file and set svn:eol-style in one command using the --auto-props and --config-option options to svn import. When I do the import I explicitly specify the file name in the import URL. The reason I do this is because I want to import from a randomly generated temp f

Re: Building Subversion 1.6.11 on AIX 6.1

On Thu, Jun 3, 2010 at 10:11 AM, Justin Johnson wrote: > Hello, > > I have been trying to compile Subversion 1.6.11 on AIX 6.1. Every time I > get a successful build, the resulting executables segfault. Does anyone > have any suggestions as to what I might be doing wrong? >

Building Subversion 1.6.11 on AIX 6.1

Hello, I have been trying to compile Subversion 1.6.11 on AIX 6.1. Every time I get a successful build, the resulting executables segfault. Does anyone have any suggestions as to what I might be doing wrong? I have gcc 4.0.0 installed but am not building with it due to some syntax errors I was

Re: Error "An existing connection was forcibly closed by the remote host" with F5 content switch or working copy on shared drive

On Fri, Mar 12, 2010 at 9:34 AM, Justin Johnson wrote: > Hi, > > I'm trying to understand why the following error occurs. > > svn: REPORT request failed on '/svn/reponame/!svn/vcc/default' > svn: REPORT of '/svn/reponame/!svn/vcc/default': Could not r

Error "An existing connection was forcibly closed by the remote host" with F5 content switch or working copy on shared drive

Hi, I'm trying to understand why the following error occurs. svn: REPORT request failed on '/svn/reponame/!svn/vcc/default' svn: REPORT of '/svn/reponame/!svn/vcc/default': Could not read response body: An existing connection was forcibly closed by the remote host. ( http://HOSTNAME