From: Stephen Bash <bash@genarts.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, Phillip Susi <psusi@cfl.rr.com>
Subject: Re: Splitting a repository but sharing the common parts of the object database
Date: Mon, 13 Dec 2010 14:50:50 -0500 (EST) [thread overview]
Message-ID: <31673515.186200.1292269850925.JavaMail.root@mail.hq.genarts.com> (raw)
In-Reply-To: <20101213192053.GA30315@burratino>
----- Original Message -----
> From: "Jonathan Nieder" <jrnieder@gmail.com>
> To: "Phillip Susi" <psusi@cfl.rr.com>
> Cc: git@vger.kernel.org
> Sent: Monday, December 13, 2010 2:20:53 PM
> Subject: Re: Splitting a repository but sharing the common parts of the object database
> Hi Phillip,
>
> Phillip Susi wrote:
>
> > 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.
>
> You might be interested in girocco's fork support. See
> http://repo.or.cz/w/girocco.git/blob/HEAD:/jobd/gc.sh for starters.
You might also be interested in Pro Git's entry on git-replace:
http://progit.org/2010/03/17/replace.html
It's a completely different approach than what you're suggesting, but might open up new and interesting avenues.
Stephen
next prev parent reply other threads:[~2010-12-13 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 18:39 Splitting a repository but sharing the common parts of the object database Phillip Susi
2010-12-13 19:20 ` Jonathan Nieder
2010-12-13 19:50 ` Stephen Bash [this message]
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=31673515.186200.1292269850925.JavaMail.root@mail.hq.genarts.com \
--to=bash@genarts.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=psusi@cfl.rr.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).