From: Sam Vilain <sam@vilain.net>
To: Marcus Better <marcus@better.se>
Cc: git@vger.kernel.org
Subject: Re: git-svn not fetching all revisions
Date: Wed, 11 Nov 2009 17:00:48 +1300 [thread overview]
Message-ID: <4AFA36F0.6070501@vilain.net> (raw)
In-Reply-To: <4AF9AC1A.5000100@better.se>
Marcus Better wrote:
> The problem is that the trunk was replaced by a branch at some point.
> When I do "git svn clone -s svn://host/repo/project" it only fetches the
> "old" trunk up to the time of the switch, and then stops. Newer
> revisions of the "new" trunk are not fetched and cannot be seen with
> "find-rev".
Yeah. Try doing it in parts - fetch the two stages of the history
explicitly using the revision range arguments to 'git svn fetch' - and
then graft the histories together and fix up with git filter-branch. A
bit of a hassle, but unfortunately there's not much other option...
Sam
next prev parent reply other threads:[~2009-11-11 4:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 18:08 git-svn not fetching all revisions Marcus Better
2009-11-11 4:00 ` Sam Vilain [this message]
2009-11-19 12:07 ` Marcus Better
2009-11-20 4:12 ` [spf:guess] " Sam Vilain
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=4AFA36F0.6070501@vilain.net \
--to=sam@vilain.net \
--cc=git@vger.kernel.org \
--cc=marcus@better.se \
/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).