On Wed, Apr 29, 2020 at 7:14 AM Chaya wrote:
>
> 1. Unfortunately, it's not a public repository.
> 2. The SVN project repo is actually file based. So I had to convert it to
> svn protocol before cloning to git.
> 3. Using latest version of svn (version 1.13.0 (r1867053)) and git ( version
> 1.13.0
Johan Corveleyn wrote on Wed, 29 Apr 2020 11:04 +0200:
> On Wed, Apr 29, 2020 at 7:14 AM Chaya wrote:
> >
> > 1. Unfortunately, it's not a public repository.
> > 2. The SVN project repo is actually file based. So I had to convert it to
> > svn protocol before cloning to git.
> > 3. Using latest ve
On Wed, Apr 29, 2020 at 12:11 PM Daniel Shahaf wrote:
>
> Johan Corveleyn wrote on Wed, 29 Apr 2020 11:04 +0200:
> > On Wed, Apr 29, 2020 at 7:14 AM Chaya wrote:
> > >
> > > 1. Unfortunately, it's not a public repository.
> > > 2. The SVN project repo is actually file based. So I had to convert i
Johan Corveleyn wrote on Wed, 29 Apr 2020 12:23 +0200:
> On Wed, Apr 29, 2020 at 12:11 PM Daniel Shahaf
> wrote:
> > Johan, what do you mean by 'a very old format which isn't supported well
> > by "git svn"'?
>
> For instance an svn repository that was created by svnadmin 1.0, with
> BDB backe
How do I update source if when I use Svn update it responds with svn: e155007
none of the targets are working copies.
On Wed, Apr 29, 2020 at 1:10 PM Brandon Helsley
wrote:
> How do I update source if when I use Svn update it responds with svn:
> e155007 none of the targets are working copies.
>
Are you using the svn command line client or a GUI?
If the command line client, are you in a working copy directory w
Nathan Hartman:
> If the command line client, are you in a working copy directory
> when you run the "svn update" command?
That was my initial suggestion, too, but when I tried `svn up' at a
random location that was not an SVN working directory it printed:
Skipped '.'
Summary of conflicts:
On Wed, Apr 29, 2020 at 6:42 PM Anton Shepelev wrote:
>
> Nathan Hartman:
>
> > If the command line client, are you in a working copy directory
> > when you run the "svn update" command?
>
> That was my initial suggestion, too, but when I tried `svn up' at a
> random location that was not an SVN w
Hi all,
Thanks for all the suggestions and hints given.
The problem is finally solved.
Here is my analysis:
I copied the SVN repository to my local machine (which was on network drive
before).
The 'git svn clone' command does not work for file based repository. And
this is why I had to convert t
