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

Re: What is the best way to backport a feature?

From
Pascal Obry <pascal@obry.net>
Date
Nov 29, 2009, 16:52 UTC
Message-ID
<4B12A6E8.8050803@obry.net>
In-Reply-To
<20091129164748.GB7921@atjola.homenet>
Le 29/11/2009 17:47, Björn Steinbrink a écrit :
> What's unusual there is that you merged from Mainline to Feature_A.
> Usually, the history would look like this:

Right, I missed that! It is indeed very unusual at the point that I missed to read it properly :) So my reply is wrong.

Pascal.
-- 
--|------------------------------------------------------
--| Pascal Obry                           Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--|    http://www.obry.net  -  http://v2p.fr.eu.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Previous: Björn SteinbrinkNext: Pascal Obry
Message 3 of 10 in “What is the best way to backport a feature?”
  1. Peter WeselohNov 29, 2009
  2. Björn SteinbrinkNov 29, 2009
  3. Pascal ObryNov 29, 2009
  4. Pascal ObryNov 29, 2009
  5. Michael J GruberNov 29, 2009
  6. Greg A. WoodsNov 30, 2009
  7. Fwd: What is the best way to backport a feature?Peter Weseloh, Nov 29, 2009
  8. Johannes SixtNov 29, 2009
  9. Peter WeselohNov 29, 2009
  10. Björn SteinbrinkNov 29, 2009

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.