Re: dangling blob which is not dangling at all

On Wed, Aug 01, 2007 at 11:13:27AM +0200, Rogan Dawes wrote:

Steven Grimm wrote:

quoted

Domenico Andreoli wrote:

quoted

What is this reflog thing and why is required?
  

It is a log of where each ref pointed at any given time. Or rather, a log 
of changes to refs, with timestamps. It is not *required* per se (you can 
turn it off and almost all of git will continue to work as before) but 
it's handy in that you can say stuff like
git checkout -b newbranch master@"{4 days ago}"
and git will give you a new branch pointing at the rev that master pointed 
to 4 days ago, even if it's a rev that is no longer reachable from any of 
the existing heads (e.g., because you did a "git rebase" and the rev in 
question was replaced by a new one.) Obviously as soon as you do a "git 
gc" you will lose the ability to go back to unreachable revs using the 
reflog.

Not strictly true. "git gc" does take the reflogs into account when 
determining reachability, but it also prunes the reflogs periodically to 
prevent them from growing without bound (and preventing pruning of 
otherwise unreachable objects).

so, besides playing with head refs by hand and forcing pushing to
"not strict subset" heads, having dangling commits may be physiologic?

and the only way to leak commits is from heads? on the countary, has
one a severely broken repository?

many thanks,
Domenico

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