Thread (5 messages) flat view 5 messages, 4 authors, 2016-06-15

Re: dangling blob which is not dangling at all

From: Domenico Andreoli <hidden>
Date: 2016-06-15 22:43:25

On Wed, Aug 01, 2007 at 12:27:10AM -0700, Junio C Hamano wrote:
Domenico Andreoli [off-list ref] writes:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help