* Import of svn rep has path issues
@ 2010-05-01 13:45 Paulo J. Matos
2010-05-02 8:15 ` Ulrich Spörlein
0 siblings, 1 reply; 3+ messages in thread
From: Paulo J. Matos @ 2010-05-01 13:45 UTC (permalink / raw)
To: git
Hi all,
I just tried to import a svn project into git using git-svnimport.
I followed:
http://weblog.redlinesoftware.com/2008/2/24/converting-subversion-repositories-to-git
The line was:
git-svnimport -C projname -r -v -A authors https://your-repo-host.com/projname
Interestingly some revisions resulted in a lot of errors with:
91: Unrecognized path: /main.cc
This seems to occur in the first revisions where I hadn't adopted a tree
format of /branches, /tags, /trunk.
On the other hand, git-svnimport returned 0 to the environment, so I
would assume that those 'Unrecognized path' issues are just warnings and
everything went fine. I would like to have some confirmation of this if
possible and if these files were not imported into my new git rep, how
can I solve these issues?
Thanks,
--
PMatos
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Import of svn rep has path issues
2010-05-01 13:45 Import of svn rep has path issues Paulo J. Matos
@ 2010-05-02 8:15 ` Ulrich Spörlein
2010-05-04 9:01 ` Paulo J. Matos
0 siblings, 1 reply; 3+ messages in thread
From: Ulrich Spörlein @ 2010-05-02 8:15 UTC (permalink / raw)
To: Paulo J. Matos; +Cc: git
On Sat, 01.05.2010 at 14:45:00 +0100, Paulo J. Matos wrote:
> Hi all,
>
> I just tried to import a svn project into git using git-svnimport.
> I followed:
> http://weblog.redlinesoftware.com/2008/2/24/converting-subversion-repositories-to-git
>
> The line was:
> git-svnimport -C projname -r -v -A authors https://your-repo-host.com/projname
>
> Interestingly some revisions resulted in a lot of errors with:
> 91: Unrecognized path: /main.cc
>
> This seems to occur in the first revisions where I hadn't adopted a tree
> format of /branches, /tags, /trunk.
> On the other hand, git-svnimport returned 0 to the environment, so I
> would assume that those 'Unrecognized path' issues are just warnings and
> everything went fine. I would like to have some confirmation of this if
> possible and if these files were not imported into my new git rep, how
> can I solve these issues?
Well, just look at your git-repo then and see if the logs indicate this
file made it (I doubt it).
Please have a look at svn2git, which can take rules for what to do with
specific paths at specific revisions. This should make it possible to go
from
/ is master in git
to
/trunk is master in git
with little effort
Regards,
Uli
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Import of svn rep has path issues
2010-05-02 8:15 ` Ulrich Spörlein
@ 2010-05-04 9:01 ` Paulo J. Matos
0 siblings, 0 replies; 3+ messages in thread
From: Paulo J. Matos @ 2010-05-04 9:01 UTC (permalink / raw)
To: git
Ulrich Spörlein <uqs@spoerlein.net> writes:
>
> Well, just look at your git-repo then and see if the logs indicate this
> file made it (I doubt it).
>
Indeed it didn't make it which is unfortunate.
> Please have a look at svn2git, which can take rules for what to do with
> specific paths at specific revisions. This should make it possible to go
> from
>
Thanks for the svn2git ref. My issue seems to be that my svn rep has
been used for all sorts of stuff: docs, general files, source code and
therefore I have actually never followed the branches/, tags/, trunk/
git-svnimport requires. Do you know if svn2git allows you to import an
svn repository with all revisions as is even if they don't follow normal
path conventions for software repositories?
Cheers,
--
PMatos
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-05-04 9:02 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-01 13:45 Import of svn rep has path issues Paulo J. Matos
2010-05-02 8:15 ` Ulrich Spörlein
2010-05-04 9:01 ` Paulo J. Matos
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).