From: Graeme Geldenhuys <graemeg@gmail.com>
To: git@vger.kernel.org
Subject: Re: 'git svn fetch' keeps giving a error after freezing
Date: Thu, 09 Jul 2009 14:46:27 +0200 [thread overview]
Message-ID: <h34ors$g55$1@ger.gmane.org> (raw)
In-Reply-To: <20090709093412.GA30076@nan92-1-81-57-214-146.fbx.proxad.net>
Yann Dirson wrote:
> I ran an "svn clone -s http://svn2.freepascal.org/svn/fpc" yesterday,
> and it went through all 13373 revs without a problem. The freeze you
> talk about must have done something weird to the git-svn metadata.
>
That is weird. Two of you got it right without issues.... I'm trying
again, using a new repository directory and see what happens. Like you
said, maybe the original one got corrupt or something.
I'm using the following command:
$ git svn clone -s --authors-file=/mnt/samba/git/fpc-users.txt \
http://svn2.freepascal.org/svn/fpc fpc_new.git
Lets hope it goes through this time. I'll report on my progress later.
If this doesn't work, I'll try it without the --authors-file option.
If it doesn't go well, any chance you still have that FPC repository
lying around? Would it then be possible for you to repack the repository
and archive (zip, bzip, 7zip etc..) the repository so I could download
the whole thing from you? But this is ONLY if my new attempt doesn't work.
I'm hoping all will go well though, otherwise I am totally stumped as to
why I can't clone it myself.
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://opensoft.homeip.net/fpgui/
next prev parent reply other threads:[~2009-07-09 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 11:21 'git svn fetch' keeps giving a error after freezing Graeme Geldenhuys
2009-07-08 23:59 ` Eric Wong
2009-07-09 8:51 ` Graeme Geldenhuys
2009-07-09 8:52 ` Graeme Geldenhuys
2009-07-09 9:34 ` Yann Dirson
2009-07-09 12:46 ` Graeme Geldenhuys [this message]
2009-07-09 12:01 ` Michael J Gruber
2009-07-10 7:07 ` Graeme Geldenhuys
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='h34ors$g55$1@ger.gmane.org' \
--to=graemeg@gmail.com \
--cc=git@vger.kernel.org \
/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).