git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Splitting a repository but sharing the common parts of the object database

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Dec 13, 2010, 19:20 UTC
Message-ID
<20101213192053.GA30315@burratino>
In-Reply-To
<4D066873.4020208@cfl.rr.com>
Hi Phillip,
Phillip Susi wrote:
Show 7 quoted lines
> 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.

(Yes, the short answer is "-l" but showing where I got that answer from seems a little easier. :))

Previous: Phillip SusiNext: Stephen Bash
Message 2 of 5 in “Splitting a repository but sharing the common parts of the object database”
  1. Phillip SusiDec 13, 2010
  2. Jonathan NiederDec 13, 2010
  3. Stephen BashDec 13, 2010
  4. Phillip SusiDec 13, 2010
  5. Jonathan NiederDec 13, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.