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

Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?

From
Shawn Pearce <spearce@spearce.org>
Date
Nov 21, 2006, 16:56 UTC
Message-ID
<20061121165656.GC22006@spearce.org>
In-Reply-To
<45632EC6.5030902@freescale.com>
Timur Tabi <timur@freescale.com> wrote:
Show 6 quoted lines
> >Shallow clone is a development feature still being working on in
> >Junio's 'pu' branch of git.git.  It has a few issues still to be
> >worked out so it hasn't been made part of one of the more stable
> >branches yet (like 'next', 'master', or 'maint').
> 
> Well, until it's available on an official git release, it doesn't help me.

One of the reasons its hanging out in 'pu' still is that there is a lack of people who are interested in the feature, and thus not enough people are testing it. Perhaps you might be able to lend a hand in that regard?

Previous: Timur TabiNext: Timur Tabi
Message 9 of 19 in “Is there a way to trim old SHAs from a git tree (so it's not so large)?”
  1. Timur TabiNov 15, 2006
  2. Shawn PearceNov 15, 2006
  3. Timur TabiNov 15, 2006
  4. Shawn PearceNov 15, 2006
  5. Thomas KolejkaNov 17, 2006
  6. Timur TabiNov 21, 2006
  7. Shawn PearceNov 21, 2006
  8. Timur TabiNov 21, 2006
  9. Shawn PearceNov 21, 2006
  10. Timur TabiNov 21, 2006
  11. Shawn PearceNov 21, 2006
  12. Timur TabiNov 21, 2006
  13. Johannes SchindelinNov 21, 2006
  14. Timur TabiNov 21, 2006
  15. Jakub NarebskiNov 21, 2006
  16. Johannes SchindelinNov 21, 2006
  17. Timur TabiNov 21, 2006
  18. Jakub NarebskiNov 21, 2006
  19. Johannes SchindelinNov 21, 2006

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.