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

Re: Applying patches from a patch set

From
Jakub Narebski <jnareb@gmail.com>
Date
Dec 20, 2008, 19:25 UTC
Message-ID
<m3iqped4yi.fsf@localhost.localdomain>
In-Reply-To
<dac45060812200637m49c71aa5x3c25010fa00f4a63@mail.gmail.com>
"Mark Ryden" <markryde@gmail.com> writes:
>   I am subscribed to some linux kernel subsystem mailing list; in this
> list there are sometimes patchsets with more than
> 30-40 patches.
I hope in proper patch series...
> I am using gmail web interface client.

Better use some standalone mail program. Patch series should be send in thread, either as reply to the cover letter message, or threaded each being reply to previous patch... beside being numbered; IIRC GMail web interface doesn't have threading implemented...

> In order to apply a patch set I copy and paste each patch from the
> patchset into a file, and then apply that patch.

You use raw view, I assume? Otherwise you would fail afoul word wrapping and other whitespace mangling, at least...

[...]
> (I remember there was something called git apply-mbox in the past).

You can use "git am" for that, which is modern equivalent, and which can do (almost) everything git-apply-mbox did.

-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: Mark RydenNext: Junio C Hamano
Message 2 of 7 in “Applying patches from a patch set”
  1. Mark RydenDec 20, 2008
  2. Jakub NarebskiDec 20, 2008
  3. Junio C HamanoDec 20, 2008
  4. Mark RydenDec 23, 2008
  5. Sitaram ChamartyDec 21, 2008
  6. Mark RydenDec 21, 2008
  7. Jakub NarebskiDec 21, 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.