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

Re: How to merge branches except for one commit

From
Andrew Arnott <andrewarnott@gmail.com>
Date
May 29, 2008, 05:42 UTC
Message-ID
<216e54900805282242t1ac249bbv91e4166c72bbcd33@mail.gmail.com>
In-Reply-To
<7bfdc29a0805282138kabc5417i4f67ae3995bf238c@mail.gmail.com>
Yes, thanks!
On Wed, May 28, 2008 at 9:38 PM, Imran M Yousuf <imyousuf@gmail.com> wrote:
Show 18 quoted lines
>>
>> You can never plan ahead perfectly, so do not be too hard on yourself if
>> you occasionally screw up.  Cherry-picking from time to time is Ok.  With
>> practice, you will get used to it.  I juggle 5 integration branches to
>> maintain git.git itself and it took some practice for me to get
>> comfortable with the workflow.
>>
>
> I always wanted to know how you did it, thanks for sharing it :).
>
> Best regards,
>
> --
> Imran M Yousuf
> Email: imran@smartitengineering.com
> Blog: http://imyousuf-tech.blogs.smartitengineering.com/
> Mobile: +880-1711402557
>
-- 
Andrew Arnott
Previous: Imran M Yousuf
Message 7 of 7 in “How to merge branches except for one commit”
  1. Andrew ArnottMay 29, 2008
  2. Avery PennarunMay 29, 2008
  3. Andrew ArnottMay 29, 2008
  4. Andreas EricssonMay 29, 2008
  5. Junio C HamanoMay 29, 2008
  6. Imran M YousufMay 29, 2008
  7. Andrew ArnottMay 29, 2008

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.