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

Re: [PATCH] Add "--expire <time>" option to 'git prune'

From
Jeff King <peff@peff.net>
Date
Nov 29, 2007, 15:12 UTC
Message-ID
<20071129151211.GB32296@coredump.intra.peff.net>
In-Reply-To
<Pine.LNX.4.64.0711291419350.27959@racer.site>
On Thu, Nov 29, 2007 at 02:21:23PM +0000, Johannes Schindelin wrote:
Show 7 quoted lines
> This patch adds a mode to expire only loose, unreachable objects
> which are older than a certain time.  For example, by
> 
> 	git prune --expire 14.days
> 
> you can prune only those objects which are loose, unreachable
> and older than 14 days (and thus probably outdated).
Does this now make git-prune safe for automatic running?

I suppose you could still be actively manipulating refs that point to very old objects.

-Peff
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 11 of 14 in “[RFC] Alternates and broken repos: A pack and prune scheme to avoid them”
  1. Johannes SixtNov 18, 2007
  2. Junio C HamanoNov 18, 2007
  3. Johannes SixtNov 18, 2007
  4. Junio C HamanoNov 18, 2007
  5. Teach repack to optionally retain otherwise lost objectsJohannes Schindelin, Nov 29, 2007
  6. Junio C HamanoNov 29, 2007
  7. Johannes SchindelinNov 29, 2007
  8. Add "--expire <time>" option to 'git prune'Johannes Schindelin, Nov 29, 2007
  9. Johannes SixtNov 29, 2007
  10. Add "--expire <time>" option to 'git prune'Johannes Schindelin, Nov 29, 2007
  11. Jeff KingNov 29, 2007
  12. Johannes SchindelinNov 29, 2007
  13. Junio C HamanoNov 29, 2007
  14. Add "--expire <time>" option to 'git prune'Johannes Schindelin, Nov 29, 2007

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.