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

Re: Thinning a repository

From
YDYuri D'Elia <wavexx@thregr.org>
Date
Nov 30, 2014, 12:35 UTC
Message-ID
<m5f2up$554$1@ger.gmane.org>
In-Reply-To
<20141130123400.GG31751@paksenarrion.iveqy.com>
On 11/30/2014 01:34 PM, Fredrik Gustafsson wrote:
Show 6 quoted lines
> On Sun, Nov 30, 2014 at 01:18:34PM +0100, Yuri D'Elia wrote:
>> Is there a quick way to reproduce the effect of a shallow clone on a
>> local repository that doesn't involve filter-branch and/or re-clone?
> 
> I'm curious, why is it a bad thing to do a re-clone? If you clone your
> local repo it would be really fast.

I see no reason to involve the workspace. I would also want to keep the current remote/origin as it is.

I expect a 'thin' command to be faster by not touching the workspace at all.
Previous: Fredrik Gustafsson
Message 3 of 3 in “Thinning a repository”
  1. Yuri D'EliaNov 30, 2014
  2. Fredrik GustafssonNov 30, 2014
  3. Yuri D'EliaNov 30, 2014

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.