From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Markus Heidelberg <markus.heidelberg@web.de>,
gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH] bash completion: remove deprecated --prune from git-gc
Date: Sun, 14 Dec 2008 03:23:39 -0800 (PST) [thread overview]
Message-ID: <m3hc57dmrl.fsf@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.1.00.0812141137350.2014@eeepc-johanness>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 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
prev parent reply other threads:[~2008-12-14 11:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-13 19:08 [PATCH] bash completion: remove deprecated --prune from git-gc Markus Heidelberg
2008-12-14 10:38 ` Johannes Schindelin
2008-12-14 11:12 ` Jeff King
2008-12-14 11:17 ` Johannes Schindelin
2008-12-14 11:19 ` Jeff King
2008-12-15 18:06 ` Brandon Casey
2008-12-15 16:51 ` Brandon Casey
2008-12-14 11:23 ` Jakub Narebski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3hc57dmrl.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=markus.heidelberg@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).