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

Re: History messup

From
TGThomas Gleixner <tglx@linutronix.de>
Date
May 11, 2005, 17:09 UTC
Message-ID
<1115831345.22180.75.camel@tglx>
In-Reply-To
<3772.10.10.10.24.1115676539.squirrel@linux1>
On Mon, 2005-05-09 at 18:08 -0400, Sean wrote:
> On Mon, May 9, 2005 3:34 pm, H. Peter Anvin said:
> Seems the only solution is a full search of the history, unless there is
> some clever way to label branches or detect fast forward heads.

You can apply some heuristic guessing to detect fast forward heads, but at the very end you will end up with manual selection puzzles.

On one hand we keep care to track the source of a change in the kernel code by adding signed,acked but on the other hand we don't care about history correctness. If you look at some file revisions, which you read from the tree history then you just have patches applied in the wrong order.

Maybe nobody cares, but for maintaining customer trees with a bugfix, stable and experimental branch it's necessary to keep track of information in a consistent way especially if you have to deal with the QA department.

I know that there is no simple and fool proof solution for this problem, but some band-aid to make the reconstruction of history simpler would be not too bad. 

tglx
Previous: SeanNext: Petr Baudis
Message 10 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.