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

Re: collapsing old git history to reduce repo size, while preserving commit #s and tags

From
Duy Nguyen <pclouds@gmail.com>
Date
Oct 30, 2013, 16:06 UTC
Message-ID
<CACsJy8BcJMTeyku-37v5pwVvYFixaP2sLMQ24WaerKf8C9-AAw@mail.gmail.com>
In-Reply-To
<52712BF2.2080409@gmail.com>
On Wed, Oct 30, 2013 at 10:55 PM, Jakub Narębski <jnareb@gmail.com> wrote:
Show 9 quoted lines
> On 2013-10-30 08:52, Stas Cherkassky wrote:
>>
>>
>> Shallow clone (if that's what you meant) is not suitable because it
>> doesn't allow to push/pull to/from this shallow repository.
>
>
> Still?  I think there were some work on making shallow clone to
> allowing push/pull to/from it.

Yes, still :-) I've got a proof of concept, but it needs more work to address the concern about its automatically turning a full repo into a shallow one.

-- 
Duy
Previous: Jakub Narębski
Message 5 of 5 in “Re: collapsing old git history to reduce repo size, while preserving commit #s and tags”
  1. Stas CherkasskyOct 29, 2013
  2. Andrew ArdillOct 29, 2013
  3. Stas CherkasskyOct 30, 2013
  4. Jakub NarębskiOct 30, 2013
  5. Duy NguyenOct 30, 2013

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.