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

cg-update (cogito-0.13) bug: changed heads

From: "H. Peter Anvin" <hpa@zytor.com>
Date: 2016-06-15 22:42:05

I just found a bug in cogito-0.13, at least to the best of my 
understanding of the situation.

Simplified, the problem looks like this: two sides, A and B, pull from 
repository C.  The head of this pull we call 0.

Now commit 1 is added to A.  B pulls commit 1 from A, not though C. 
Later, A pushes commit 1 to C.

Next time B tries to pull from C, cg-update will not advance 
refs/heads/origin, even though C now has a new head.  Thus, B will think 
that C is in a different state than it actually is.

This has, for me, broken safeguards of the form "make sure you're merged 
before you pull."

	-hpa
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help