Git development
 help / color / mirror / Atom feed
From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Brandon Casey <casey@nrlssc.navy.mil>
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH] repack: make repack -a equivalent to repack -A and drop previous -a behavior
Date: Fri, 14 Nov 2008 02:48:28 +0100	[thread overview]
Message-ID: <20081114014828.GD5285@atjola.homenet> (raw)
In-Reply-To: <Dei99j9xFoGAh0A3LCO0zx3LqCb4lViSZpGvv_KGn38@cipher.nrlssc.navy.mil>

On 2008.11.13 19:36:45 -0600, Brandon Casey wrote:
> Björn Steinbrink wrote:
> > On 2008.11.13 18:53:29 -0600, Brandon Casey wrote:
> >> Björn Steinbrink wrote:
> >>> We have:
> >>> 	-a	Create a new pack, containing all reachable objects
> >>> 	-A	Same as -a
> >>> 	-ad	Same as -a, and drop all old packs and loose objects
> >> by loose objects, I assume you mean packed unreachable objects.
> > 
> > No, actually I just totally ignored the fact that -a of course already
> > deletes the loose objects.
> 
> Actually, I had forgotten that repack deletes any loose objects at all.
> It does call prune-packed, but only when -d is used.

Ugh, right. -a does not delete loose objects without -d. So, ignoring
the .keep stuff, my initial description was even right and I just
confused myself afterwards :-/

Thanks,
Björn

  reply	other threads:[~2008-11-14  1:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13 23:22 [RFC PATCH] repack: make repack -a equivalent to repack -A and drop previous -a behavior Brandon Casey
2008-11-14  0:02 ` Björn Steinbrink
2008-11-14  0:53   ` Brandon Casey
2008-11-14  1:25     ` Björn Steinbrink
2008-11-14  1:36       ` Brandon Casey
2008-11-14  1:48         ` Björn Steinbrink [this message]
2008-11-14  2:22     ` Theodore Tso
  -- strict thread matches above, loose matches on Subject: below --
2008-11-13 23:20 Brandon Casey

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=20081114014828.GD5285@atjola.homenet \
    --to=b.steinbrink@gmx.de \
    --cc=casey@nrlssc.navy.mil \
    --cc=git@vger.kernel.org \
    /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