From: Phillip Susi <psusi@cfl.rr.com>
To: git@vger.kernel.org
Subject: Splitting a repository but sharing the common parts of the object database
Date: Mon, 13 Dec 2010 13:39:47 -0500 [thread overview]
Message-ID: <4D066873.4020208@cfl.rr.com> (raw)
I have recently started a new project that has begun its life as a fork
of an old project, then heavily modified. At the same time I am looking
into migrating from svn to git. Since this is a separate project, I
thought I should split it into a separate git repository and keep them
separate going forward, however, since they have common ancestry up to
this point, I would like to make sure that all of that data is not
duplicated.
I thought what I could do is set up an initial repository that is fully
packed and use it as a read only archive to contain all of the shared
history, then clone that into two new repositories for the two separate
projects. It seems like I can do this by running a clone -s so that the
archive is set up to be an alternate object store, then its big pack
file will be found and used for all of the old history, but new commits
will be specific to each of the two new respective projects. The
problem I run into though, is when it comes time to repack the new projects.
If I run a repack -a, then the new project has everything copied out of
the archive and into its new main pack, rather than continuing to use
the archive repository for old history, and just pack everything since
then. I guess I am looking for is somewhere between a full repack and
an incremental; a way to make repack -a discard existing local packs,
but to respect the alternate packs and omit objects they contain from
the new local pack. Is this possible?
next reply other threads:[~2010-12-13 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 18:39 Phillip Susi [this message]
2010-12-13 19:20 ` Splitting a repository but sharing the common parts of the object database Jonathan Nieder
2010-12-13 19:50 ` Stephen Bash
2010-12-13 23:17 ` Phillip Susi
2010-12-13 23:25 ` Jonathan Nieder
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=4D066873.4020208@cfl.rr.com \
--to=psusi@cfl.rr.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).