On Wed, Apr 29, 2020 at 7:14 AM Chaya <chaya.s1...@gmail.com> 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 (r1867053))
>
> --
> Sent from: 
> http://subversion.1072662.n5.nabble.com/Subversion-Users-f84423.html

You're using "git svn", which is part of git (sorry, I thought git-svn
was a separate project, but it seems to be simply part of git itself
now, as a subcommand):
https://git-scm.com/docs/git-svn

>From what I understand 2.26.2 is the latest release of git currently
(see https://git-scm.com/).

IMHO you'll need to ask the git community for support on the "git svn"
command. I have no idea what kind of svn-like operations the "git svn"
tool really performs under the hood. Maybe there are certain
pre-conditions you need to make sure of, before running "git svn" on a
repository (those should be documented at
https://git-scm.com/docs/git-svn, or if not you should ask the git
community).

Maybe one more suggestion: you say in (2) that you "had to convert it
to svn protocol before cloning to git". What do you mean with "convert
it to svn protocol"? Did you first use it as a file-based repository
(in SVN with a file:// URL), and before using "git svn" you had to set
up and "svnserve" process to serve it? Perhaps the (file-based)
repository you started from is in a very old format which isn't
supported well by "git svn". In that case, perhaps you should first
try to "svnadmin upgrade $REPO" with your svn tools, before trying to
run "git svn" on it. It's worth a try...

HTH,
-- 
Johan

Reply via email to