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

Re: Rework a patch serie

From
Karl Hasselström <kha@treskal.com>
Date
Jun 27, 2006, 10:16 UTC
Message-ID
<20060627101644.GA397@diana.vm.bytemark.co.uk>
In-Reply-To
<20060627084130.28886.qmail@web25814.mail.ukl.yahoo.com>
On 2006-06-27 08:41:30 +0000, moreau francis wrote:
Show 7 quoted lines
> Then I submit these patches for reviewing. Unfortunately, they're
> not perfect, so after some feedbacks from the communauty it appears
> that I need to make small modifications in the second commit in the
> topic branch for example...
>
> What is the best and fastest way to do that ? Should I create a new
> topic branch and cherry pick from the old one ?

stgit is a good fit for this situation. You just pop patches off the stack untill you reach the one you want to modify, then do your changes, refresh the patch, and push the other patches back. (If you want to keep the original series for future reference, you can simply tag HEAD before you embark on this procedure.)

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Previous: Andreas Ericsson
Message 3 of 3 in “Rework a patch serie”
  1. moreau francisJun 27, 2006
  2. Andreas EricssonJun 27, 2006
  3. Karl HasselströmJun 27, 2006

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.