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

Re: how to create v2 patch

From
Jakub Narebski <jnareb@gmail.com>
Date
Dec 1, 2007, 14:02 UTC
Message-ID
<m3r6i6wm1g.fsf@roke.D-201>
In-Reply-To
<47515693.9070405@imap.cc>
Tilman Schmidt <tilman@imap.cc> writes:
Show 5 quoted lines
> Let's say that following the scheme laid out in
> "Everyday GIT ...", chapter "Individual Developer (Participant)".
> I have produced a patch, submitted it to LKML, received a few
> comments, committed appropriate changes to my local git tree,
> and now want to submit a revised patch. How do I do that?

If you have original commit and commit with corrections on top of it, do a squash rebase using "git rebase -i" (interactive), or do a squash merge.

In the future it would be better to just amend ("git commit --amend") original commit (or if you are using StGIT, "stg refresh" it).

-- 
Jakub Narebski
Poland
Previous: Wincent ColaiutaNext: Björn Steinbrink
Message 9 of 10 in “how to create v2 patch”
  1. Tilman SchmidtDec 1, 2007
  2. Pascal ObryDec 1, 2007
  3. Mike HommeyDec 1, 2007
  4. Tilman SchmidtDec 6, 2007
  5. Jan HudecDec 6, 2007
  6. Pascal ObryDec 6, 2007
  7. Andreas EricssonDec 6, 2007
  8. Wincent ColaiutaDec 7, 2007
  9. Jakub NarebskiDec 1, 2007
  10. Björn SteinbrinkDec 1, 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.