All of lore.kernel.org
 help / color / mirror / Atom feed
From: Domenico Andreoli <cavokz@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: git@vger.kernel.org
Subject: Re: dangling blob which is not dangling at all
Date: Wed, 1 Aug 2007 08:32:09 +0200	[thread overview]
Message-ID: <20070801063209.GA13511@raptus.dandreoli.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0707311914570.4161@woody.linux-foundation.org>

On Tue, Jul 31, 2007 at 07:22:14PM -0700, Linus Torvalds wrote:
> 
> 
> On Wed, 1 Aug 2007, Domenico Andreoli wrote:
> > 
> > $ git fsck --no-reflogs
> > dangling blob e5d444e61b834c34710ce8fb5cb176e20e5894e1
> >
> > $ git-ls-tree 70b58535361eb633d44d4f1275af3421ca6a5ed7
> > ...
> > 100644 blob e5d444e61b834c34710ce8fb5cb176e20e5894e1    link_stream.c
> 
> Have you done clones with stupid protocols (rsync and/or http)?

I do not remember having used any dump transport on this repository but
I recall having tried git-repack with the intent of git gc.

> So try "git fsck --full", and see if that changes the picture.

This did not change anything.

> The easiest fixup is likely to just do "git gc", which which do a nice 
> repack, and get rid of loose objects that are duplicates of stuff 
> that is also in a pack-file.

This fixed things and also warned about two heads referring to pruned
commits, which may be those two commits I removed by hand (I hope).

Cheers,
Domenico

-----[ Domenico Andreoli, aka cavok
 --[ http://www.dandreoli.com/gpgkey.asc
   ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50

  reply	other threads:[~2007-08-01  6:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01  1:34 dangling blob which is not dangling at all Domenico Andreoli
2007-08-01  2:22 ` Linus Torvalds
2007-08-01  6:32   ` Domenico Andreoli [this message]
2007-08-01  7:27     ` Junio C Hamano
2007-08-01  7:42       ` Domenico Andreoli
2007-08-01  8:35         ` Steven Grimm
2007-08-01  9:13           ` Rogan Dawes
2007-08-01 14:21             ` Domenico Andreoli

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=20070801063209.GA13511@raptus.dandreoli.com \
    --to=cavokz@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.