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

Re: Porcelain support for daggy-fixes?

From
Pascal Obry <pascal@obry.net>
Date
Jun 10, 2010, 14:21 UTC
Message-ID
<AANLkTikbe_0GlSkXxiSeIQl0x0tfTYmoI5RuyJPzZioM@mail.gmail.com>
In-Reply-To
<4C10EEBE.5030400@peda.net>
Mikko,
Show 9 quoted lines
> I understand that this can already be done with git. The method is
>
> 1) store the current HEAD somewhere
> 2) figure out the proper parent for the bug fix
> 3) checkout the parent
> 4) implement the fix
> 5) commit the fix
> 6) checkout HEAD
> 7) merge with the commit from step 5
I would probably create a topic/fix branch:
1) figure out the proper parent for the bug fix
2) create the fix branch and move to it
    $ git co -b fix-feature-whatever parent
3) implement the fix
4) commit the fix
5) checkout HEAD
6) merge with the commit from step 4
And also merge on release branch if needed.
Pascal.
-- 
--|------------------------------------------------------
--| Pascal Obry                           Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--|              http://www.obry.net
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595
Previous: Mikko RantalainenNext: Mikko Rantalainen
Message 2 of 3 in “Porcelain support for daggy-fixes?”
  1. Mikko RantalainenJun 10, 2010
  2. Pascal ObryJun 10, 2010
  3. Mikko RantalainenJun 11, 2010

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.