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

Re: History messup

From
TGThomas Gleixner <tglx@linutronix.de>
Date
May 9, 2005, 18:05 UTC
Message-ID
<1115661954.19236.44.camel@tglx>
In-Reply-To
<20050509170611.GJ24216@cip.informatik.uni-erlangen.de>
On Mon, 2005-05-09 at 19:06 +0200, Thomas Glanzmann wrote:
> If two repositories pull alternating from each other one has never the
> exact state the other has. They would play ping-pong and this is a bad
> thing. That was AFAIK the reason there is no COMMIT object introduced on
> 'head forward' merges.

That makes totaly sense, but for history tracking it is a horror scenario, unless you dont have head history lists per repository or an unique repository identifier in the commit blob itself.

tglx
Previous: Thomas GlanzmannNext: David Woodhouse
Message 3 of 11 in “History messup”
  1. Thomas GleixnerMay 9, 2005
  2. Thomas GlanzmannMay 9, 2005
  3. Thomas GleixnerMay 9, 2005
  4. David WoodhouseMay 9, 2005
  5. Thomas GleixnerMay 9, 2005
  6. H. Peter AnvinMay 9, 2005
  7. David WoodhouseMay 9, 2005
  8. H. Peter AnvinMay 9, 2005
  9. SeanMay 9, 2005
  10. Thomas GleixnerMay 11, 2005
  11. Petr BaudisMay 11, 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.