From: Bradley Wagner <bradley.wagner@hannonhill.com>
To: git@vger.kernel.org
Subject: SVN to Git: trunk moved during repository history
Date: Mon, 19 Apr 2010 17:18:16 -0400 [thread overview]
Message-ID: <o2i2f0f6ced1004191418i6a144652sd9ac38b07fb7b661@mail.gmail.com> (raw)
In-Reply-To: <l2x2f0f6ced1004191416jd8db7d5eyf8fc7a55f5efa2cc@mail.gmail.com>
I'm trying to port an SVN project to Git. We have gone through
multiple layouts for our SVN repository. It started off with just a
mainline branch in the root folder. Then we went to the standard
layout (branches, trunk, tags).
The problem is that when I do a "git svn clone --stdlayout" of the
repository, it's not picking up any of the revisions from when the
trunk previously resided in the root directory.
Is there any way to specify that the trunk had multiple paths the way
you can specify multiple branch folders with -b flag? What would be
the best course of action for reporting an SVN repo who's layout had
changed during its history?
Thanks,
Bradley
next parent reply other threads:[~2010-04-19 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <l2x2f0f6ced1004191416jd8db7d5eyf8fc7a55f5efa2cc@mail.gmail.com>
2010-04-19 21:18 ` Bradley Wagner [this message]
2010-04-20 0:07 ` SVN to Git: trunk moved during repository history Stephen Kelly
2010-04-21 14:03 ` Bradley Wagner
2010-04-23 15:12 ` Ulrich Spörlein
2010-04-27 19:55 ` Bradley Wagner
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=o2i2f0f6ced1004191418i6a144652sd9ac38b07fb7b661@mail.gmail.com \
--to=bradley.wagner@hannonhill.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).