From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on sa.int.altlinux.org X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 Date: Mon, 7 Dec 2009 16:17:27 +0200 From: Michael Shigorin To: sisyphus@lists.altlinux.org Message-ID: <20091207141727.GM14075@osdn.org.ua> Mail-Followup-To: sisyphus@lists.altlinux.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.2.1i Subject: Re: [sisyphus] =?koi8-r?b?UTog79vJwsvJLCDOwcrExc7O2cUgZ2l0IGZzY2s=?= X-BeenThere: sisyphus@lists.altlinux.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: shigorin@gmail.com, ALT Linux Sisyphus discussions List-Id: ALT Linux Sisyphus discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Dec 2009 14:17:42 -0000 Archived-At: List-Archive: List-Post: On Mon, Dec 07, 2009 at 07:57:41PM +0600, Michael Pozhidaev wrote: > Вот на одном гитовом репо git fsck пишет такое: > dangling blob 2635bf94eae515a20cd87fb27a4a9ce901917ded > dangling blob 3c19db0a36b61f6ee1678eeb764c11fa3547745b > О чём бы это могло говорить? Ничего страшного: --- There are also other situations that cause dangling objects. For example, a "dangling blob" may arise because you did a "git add" of a file, but then, before you actually committed it and made it part of the bigger picture, you changed something else in that file and committed that *updated* thing--the old state that you added originally ends up not being pointed to by any commit or tree, so it's now a dangling blob object. --- http://kernel.org/pub/software/scm/git/docs/user-manual.html#dangling-objects > Как-нибудь такое лечится? git prune -- ---- WBR, Michael Shigorin ------ Linux.Kiev http://www.linux.kiev.ua/