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

Re: [PATCH] bash completion: remove deprecated --prune from git-gc

From
Jakub Narebski <jnareb@gmail.com>
Date
Dec 14, 2008, 11:23 UTC
Message-ID
<m3hc57dmrl.fsf@localhost.localdomain>
In-Reply-To
<alpine.DEB.1.00.0812141137350.2014@eeepc-johanness>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 6 quoted lines
> On Sat, 13 Dec 2008, Markus Heidelberg wrote:
> 
> > -		__gitcomp "--prune --aggressive"
> > +		__gitcomp "--aggressive"
> 
> git gc --prune is deprecated?  That's news to me.
More like "git gc --prune" is no-op now.
 
> How would you suggest, then, to remove the loose objects you always get 
> with conflicts in a merge?

"git gc" does pruning of loose objects, but protected by grace period for loose objects with gc.pruneexpire

You always have (admittedly lowe level) git-prune.
-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: Brandon Casey
Message 8 of 8 in “bash completion: remove deprecated --prune from git-gc”
  1. bash completion: remove deprecated --prune from git-gcMarkus Heidelberg, Dec 13, 2008
  2. Johannes SchindelinDec 14, 2008
  3. Jeff KingDec 14, 2008
  4. Johannes SchindelinDec 14, 2008
  5. Jeff KingDec 14, 2008
  6. Brandon CaseyDec 15, 2008
  7. Brandon CaseyDec 15, 2008
  8. Jakub NarebskiDec 14, 2008

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.