From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Daniel Pocock <daniel@pocock.com.au>
Cc: git@vger.kernel.org
Subject: Re: git-svn: cloning an SVN repo with sub-branches and sub-tags
Date: Fri, 30 Mar 2012 18:05:45 +0530 [thread overview]
Message-ID: <CALkWK0k7eCTuDdjdABpYrecf7G4_ejcsNmeCxPKSN46406U_2g@mail.gmail.com> (raw)
In-Reply-To: <4F75A571.2020304@pocock.com.au>
Hi again,
Daniel Pocock wrote:
> One other factor I didn't mention in the original email, some of the
> branches have been renamed/moved within the SVN repo - is that a problem for
> git-svn?
Yes, I think so.
> One compromise I have thought about would be just extracting trunk, and
> forgetting about the branches, and manually tagging the official releases
> (as there were very few of them, this is quick)
Just use contrib/svn-fe in that case: it's really quick and
lightweight. You can then filter-branch the history and pull out
branches by hand.
> However, based on the errors/warnings, is it possible that there is any
> corruption in the gitified version of trunk (or the history of trunk)?
No corruption is possible on the Git side of things- it has
cryptographic hashes for everything.
Ram
next prev parent reply other threads:[~2012-03-30 12:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 13:47 git-svn: cloning an SVN repo with sub-branches and sub-tags Daniel Pocock
2012-03-29 14:40 ` Dave Zarzycki
2012-03-30 12:16 ` Daniel Pocock
2012-03-30 16:20 ` Dave Zarzycki
2012-03-29 15:32 ` Ramkumar Ramachandra
2012-03-30 12:22 ` Daniel Pocock
2012-03-30 12:35 ` Ramkumar Ramachandra [this message]
2012-03-29 15:56 ` dag
2012-03-29 16:03 ` Stephen Bash
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=CALkWK0k7eCTuDdjdABpYrecf7G4_ejcsNmeCxPKSN46406U_2g@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=daniel@pocock.com.au \
--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).