From: "Dave Hanson" <drh@drhanson.net>
To: "Jason Sewall" <jasonsewall@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Breaking up repositories
Date: Thu, 31 May 2007 06:55:15 -0700 [thread overview]
Message-ID: <9fb1551c0705310655r234eca96md32ce157b98eff46@mail.gmail.com> (raw)
In-Reply-To: <31e9dd080705302350x7752c1f0p3dee2f0d35a97b56@mail.gmail.com>
I had similar problem; I split my monolithic repo, monolithic-git, as follows.
1. When I did the git-svn, I ended up with git branches for each
project in my svn repo. I think I created these by hand, but I don't
recall.
2. To split project foo into its own repo, foo-git, from monolithic-git, I did:
mkdir foo-git
cd foo-git
git init
git pull ../monolithic-git foo
>From then on, I worked in foo-git. Eventually, I pitched
monolithic-git. I suspect there's a better way to do this...others
will surely chime in.
dave h
next prev parent reply other threads:[~2007-05-31 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 6:50 Breaking up repositories Jason Sewall
2007-05-31 13:55 ` Dave Hanson [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-31 15:53 Josh Triplett
2007-06-01 7:45 ` Andy Parkins
2007-06-01 10:25 ` Jakub Narebski
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=9fb1551c0705310655r234eca96md32ce157b98eff46@mail.gmail.com \
--to=drh@drhanson.net \
--cc=git@vger.kernel.org \
--cc=jasonsewall@gmail.com \
/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).