git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
HAH. Peter Anvin <hpa@zytor.com>
Date
Sep 6, 2005, 21:01 UTC
Message-ID
<431E03A5.6060709@zytor.com>

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
Next: Petr Baudis
Message 1 of 5 in “cg-update (cogito-0.13) bug: changed heads”
  1. H. Peter AnvinSep 6, 2005
  2. Petr BaudisSep 6, 2005
  3. H. Peter AnvinSep 6, 2005
  4. H. Peter AnvinSep 7, 2005
  5. Junio C HamanoSep 7, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.