git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen & Linda Smith" <ischis2@cox.net>
To: git@vger.kernel.org
Subject: git svn hangs on a rebase or clone when presented with a large commit.
Date: Wed, 10 Feb 2010 18:25:41 -0700	[thread overview]
Message-ID: <201002101825.41500.ischis2@cox.net> (raw)

I have to use git svn to pull from a subversion repository in a local git 
repository.  I don't have any local subversion repositories to debug the 
problem that I will describe below.

I do a git svn clone (or if I've already done a clone an git svn rebase) from 
the repository.   There is one particular subversion commit that is quite 
large  (revision 15300).   Anyway both the git svn clone  and the git svn 
rebase commands hang.

     ...  - r15259 - r15300 - r15301 - ...

I know there are commits in the subversion repoistory beyond the bad 
repository and I would like to be able do manually what git svn rebase would 
do with the commit and then be able to run git svn rebase to get revisions 
15301 and following.

Are the steps necessary to manually fetch 15300 so that I don't screw up 
future git svn rebase commands documented?

                 reply	other threads:[~2010-02-11  1:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201002101825.41500.ischis2@cox.net \
    --to=ischis2@cox.net \
    --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).