From: Domenico Andreoli <cavokz@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: dangling blob which is not dangling at all
Date: Wed, 1 Aug 2007 09:42:37 +0200 [thread overview]
Message-ID: <20070801074237.GA14790@raptus.dandreoli.com> (raw)
In-Reply-To: <7vhcnjbtpt.fsf@assigned-by-dhcp.cox.net>
On Wed, Aug 01, 2007 at 12:27:10AM -0700, Junio C Hamano wrote:
> Domenico Andreoli <cavokz@gmail.com> writes:
>
> > 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).
>
> Exactly.
>
> All refs under .git/refs (the special case of this includes the
> branch heads in .git/refs/heads) are your _promise_ to git that
> everything that is reachable from them are supposed to be
> available in your repository. If you remove specific commits by
> hand without adjusting the branch ref, you are breaking that
> promise and git-fsck will notice it as a repository breakage.
If I move any ref by hand (not that I pass the day doing this..), I
understand that some commits may suddenly result as unreachable. But
those commits I removed by hand were already unreachable so no refs
should have been referring them.
What is this reflog thing and why is required?
Domenico
-----[ Domenico Andreoli, aka cavok
--[ http://www.dandreoli.com/gpgkey.asc
---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50
next prev parent reply other threads:[~2007-08-01 7:42 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
2007-08-01 7:27 ` Junio C Hamano
2007-08-01 7:42 ` Domenico Andreoli [this message]
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=20070801074237.GA14790@raptus.dandreoli.com \
--to=cavokz@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.