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

Re: Opinions on bug fix organisation

From
Shawn O. Pearce <spearce@spearce.org>
Date
May 16, 2007, 21:38 UTC
Message-ID
<20070516213819.GT3141@spearce.org>
In-Reply-To
<200705162220.15417.andyparkins@gmail.com>
Andy Parkins <andyparkins@gmail.com> wrote:
Show 9 quoted lines
> What is your preference when, for example, you have already merged a 
> topic to next but then a bug fix appears?
> 
>  * -- * -- * -- M -- F         * -- * -- * -- M -- m (next)
>                /        or                   /    /
>     B -- * -- *                   B -- * -- * -- F (topic)
> 
> F is certainly most appropriate to be on the topic branch, but we create 
> a perhaps excessively verbose extra merge, m.

Look at the history of the next branch; the diagram on the right is exactly what Junio does. When topic finally graduates to master, only F is merged to master, making master's own history not show that "verbose extra merge" m. Or M really for that matter, as master gets its own M'.

-- 
Shawn.
Previous: Andy ParkinsNext: Johannes Sixt
Message 5 of 8 in “Opinions on bug fix organisation”
  1. Andy ParkinsMay 16, 2007
  2. Brian GernhardtMay 16, 2007
  3. Junio C HamanoMay 16, 2007
  4. Andy ParkinsMay 16, 2007
  5. Shawn O. PearceMay 16, 2007
  6. Johannes SixtMay 18, 2007
  7. Martin LanghoffMay 16, 2007
  8. Jan HudecMay 18, 2007

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.