Thread (1 message) 1 message, 1 author, 2016-06-15

Re: Recovering from repository corruption

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:44:43

Linus Torvalds [off-list ref] writes:
Ahh, ok. Yes, we should probably re-think our 'grafts' file thing, or at 
least not document it, because it's actually a wondeful way to just cause 
more corruption by hiding things (ie if you clone a repo with a grafts 
file, the result will now have neither the grafts file _nor_ the state 
that was hidden by it, so the result is guaranteed to be corrupt).
"Graft and then clone" will not make the copied repository Ok.  You need
to propagate the graft in some other way.

However, "Graft and then filter-branch" is a way to hide and get rid of
the the broken thing in history etched in the objects.  After that the
repository itself and a clone from it will not need the graft.  So I'd
rather argue we should document it _differently_ (or just _better_) than
not document it.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help