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

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

From
Petr Baudis <pasky@suse.cz>
Date
Sep 6, 2005, 23:17 UTC
Message-ID
<20050906231756.GC26934@pasky.ji.cz>
In-Reply-To
<431E03A5.6060709@zytor.com>

Dear diary, on Tue, Sep 06, 2005 at 11:01:25PM CEST, I got a letter where "H. Peter Anvin" <hpa@zytor.com> told me that...

Show 12 quoted lines
> 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.

So, C surely has its head updated? Does cg-update "fail" silently, or does it utter anything?

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone.  -- Alan Cox
Previous: H. Peter AnvinNext: H. Peter Anvin
Message 2 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.