From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Steven Line <sline00@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git svn clone terminating prematurely (I think)
Date: Wed, 11 Jan 2012 10:04:26 +0530 [thread overview]
Message-ID: <CALkWK0nyc6NVE7Qpvbc0dXb1UHGM_=uYbCS+a53HZxiBRG9HvQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ1a7SrkDOyNRv8Spo4xvoKjP4zaXteim4h3JGcWU-nYDugx9Q@mail.gmail.com>
Hi Steven,
Steven Line wrote:
> First off I am a new user to git, I'm not a git developer or power
> user. Am I in the right mailing list? If not could somebody point me
> where I could get some help from experienced git people?
This is the right place. The Git community believes in maintaining
just one mailing list.
> I need some help getting my subversion repository cloned over to git.
> Our svn repository has about 12,000 commits, when I run
> git svn clone -s -A authors.txt
> svn+ssh://csvn <at> source.res.ourdomain.com/home/svn/sem sem
> It runs for about 2h 15m then completes with no error messages. I have
> also cloned starting at revision 6300, about the middle of the svn
> repository, and I get the same results as below.
> $ git branch -a # shows only about half the branches that should have
> been cloned
Interesting. From the git-svn-id of the most recent commit, can you
tell if there's anything especially fishy about the revision where
git-svn stops? Your Subversion repository is probably broken in some
way, but git-svn should not use that as an excuse for appearing to
finish successfully while failing in reality.
Cheers.
-- Ram
next prev parent reply other threads:[~2012-01-11 4:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 0:02 git svn clone terminating prematurely (I think) Steven Line
2012-01-11 4:34 ` Ramkumar Ramachandra [this message]
2012-01-11 21:52 ` Steven Line
2012-01-11 22:48 ` Jonathan Nieder
2012-01-12 18:25 ` Steven Line
2012-01-13 7:10 ` Steven Michalske
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALkWK0nyc6NVE7Qpvbc0dXb1UHGM_=uYbCS+a53HZxiBRG9HvQ@mail.gmail.com' \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=sline00@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).