RE: dangling commits and blobs: is this normal?

From: John Dlugosz <jdlugosz@tradestation.com>
Date: Apr 22, 2009, 20:15 UTC
Message-ID: <450196A1AAAE4B42A00A8B27A59278E70ACE07F3@EXCHANGE.trad.tradestation.com>
In-Reply-To: <20090422152719.GA12881@coredump.intra.peff.net>

Show 15 quoted lines

> -----Original Message-----
> From: Jeff King [mailto:peff@peff.net]
> Sent: Wednesday, April 22, 2009 10:27 AM
> To: John Dlugosz
> Cc: git@vger.kernel.org
> Subject: Re: dangling commits and blobs: is this normal?
> 
> 
> gc will leave dangling loose objects for a set expiration time
> (defaulting to two weeks). This makes it safe to run even if there are
> operations in progress that want those dangling objects, but haven't
> yet
> added a reference to them (as long as said operation takes less than
> two
> weeks).

Ah, very enlightening.  I see: it's not just reflog stuff (which gc should know are root entry points and not complain about), it really does leave uncollected garbage on purpose, in case something is in progress.

--John

TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.