From: Stephen Bash <bash@genarts.com>
To: Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>
Cc: git@vger.kernel.org
Subject: Re: svn to git with non-standard layout
Date: Wed, 23 Nov 2011 15:22:14 -0500 (EST) [thread overview]
Message-ID: <2d5f33eb-c1dc-491a-a8ed-e8ceaaf2e2b1@mail> (raw)
In-Reply-To: <jajh7m$it7$1@dough.gmane.org>
----- Original Message -----
> From: "Bernd Schubert" <bernd.schubert@itwm.fraunhofer.de>
> To: git@vger.kernel.org
> Sent: Wednesday, November 23, 2011 2:23:34 PM
> Subject: svn to git with non-standard layout
>
> So we have something like this:
>
> svn-root -> main-project
> / | \
> / | \
> proj1 proj2 proj{n}
> / \ / \ / \
> / \ / \ trunk tags
> / \ trunk tags
> trunk tags
> / \
> tag1 tag{2...n}
Just for clarification: are there files and/or directories in main-project that are not sub-projects?
Thanks,
Stephen
next prev parent reply other threads:[~2011-11-23 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 19:23 svn to git with non-standard layout Bernd Schubert
2011-11-23 20:22 ` Stephen Bash [this message]
2011-11-23 20:52 ` Bernd Schubert
2011-11-23 21:19 ` Frans Klaver
2011-11-23 21:45 ` Bernd Schubert
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=2d5f33eb-c1dc-491a-a8ed-e8ceaaf2e2b1@mail \
--to=bash@genarts.com \
--cc=bernd.schubert@itwm.fraunhofer.de \
--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).