Re: Regression and failure to clone/fetch with new code Re: git-svn performance

2014-10-30 Thread Hin-Tak Leung
(apology for the empty message again - sticky fingers in smart phone...) -- On Thu, Oct 30, 2014 08:46 GMT Eric Wong wrote: >Thanks, I'm not able to reproduce the issue, but can you try the >following? > >diff --git a/perl/Git/SVN/Ra.pm b/perl/Git/SVN/Ra.pm >index 75cd

Re: Regression and failure to clone/fetch with new code Re: git-svn performance

2014-10-30 Thread Hin-Tak Leung
-- On Thu, Oct 30, 2014 08:46 GMT Eric Wong wrote: >Hin-Tak Leung wrote: >> Here is the data dumper info . I tried the dumper code on the R repo >> as well, and saw that against the virtual box repo, there is one >> curious difference - $self->{last_rev} is a str

Re: Regression and failure to clone/fetch with new code Re: git-svn performance

2014-10-30 Thread Eric Wong
Hin-Tak Leung wrote: > Here is the data dumper info . I tried the dumper code on the R repo > as well, and saw that against the virtual box repo, there is one > curious difference - $self->{last_rev} is a string rather than a number. > I tried hacking around doing "$x += 0;" to coerce last_rev >

Re: Regression and failure to clone/fetch with new code Re: git-svn performance

2014-10-29 Thread Hin-Tak Leung
Here is the data dumper info . I tried the dumper code on the R repo as well, and saw that against the virtual box repo, there is one curious difference - $self->{last_rev} is a string rather than a number. I tried hacking around doing "$x += 0;" to coerce last_rev to a number at various places bu

Re: Regression and failure to clone/fetch with new code Re: git-svn performance

2014-10-29 Thread Eric Wong
Hin-Tak Leung wrote: > Argh, sorry. I thought I included the info but I didn't. Thanks. I'll try a different version of svn later. > What do you think were missing in my e-mails? I was skimming and missed the part about Debian packages :) -- To unsubscribe from this list: send the line "unsubsc

Re: Regression and failure to clone/fetch with new code Re: git-svn performance

2014-10-29 Thread Hin-Tak Leung
nces of new clone against old is a missing merge in at R-2-14-branch@58454 , and two extra merges at djm-parseRd@46925 and djm-parseRd@46906 . On Wed, 29/10/14, Eric Wong wrote: Subject: Re: Regression and failure to clone/fetch with new code Re:

Re: Regression and failure to clone/fetch with new code Re: git-svn performance

2014-10-29 Thread Eric Wong
Hin-Tak Leung wrote: > Hi, I patched my system git with the recent git-svn improvements, and just use > it for general use; so theses are the patches, against 2.1.0. > > 0001-git-svn-only-look-at-the-new-parts-of-svn-mergeinfo.patch > 0002-git-svn-only-look-at-the-root-path-for-svn-mergeinfo.patc

Regression and failure to clone/fetch with new code Re: git-svn performance

2014-10-28 Thread Hin-Tak Leung
Hi, I patched my system git with the recent git-svn improvements, and just use it for general use; so theses are the patches, against 2.1.0. 0001-git-svn-only-look-at-the-new-parts-of-svn-mergeinfo.patch 0002-git-svn-only-look-at-the-root-path-for-svn-mergeinfo.patch 0003-git-svn-reduce-check_cher