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

Re: Figuring out which patches have been applied

From
Julian Phillips <julian@quantumfyre.co.uk>
Date
Oct 2, 2009, 18:45 UTC
Message-ID
<alpine.LNX.2.00.0910021944040.28646@reaper.quantumfyre.co.uk>
In-Reply-To
<9e4733910910020736n539f4331nfd61175b275c7d28@mail.gmail.com>
On Fri, 2 Oct 2009, Jon Smirl wrote:
Show 10 quoted lines
> I have a stack of 100 patches against 2.6.30. A lot of these got
> merged between 2.6.30-32.  How can I tell which ones have been
> applied?
>
> It doesn't work to check if patch A has been applied to 2.6.32. Other
> patches may have been applied on top of patch A obscuring it.
>
> Once solution would be to rebase the patch stack forward one commit at
> a time. That solves the problem of later patches obscuring patch A. Is
> there a better way to do this?

Have you tried using git-cherry? I belive that it was intended for this purpose?

-- 
Julian

  ---
Progress might have been all right once, but it's gone on too long.
 		-- Ogden Nash
Previous: Jon SmirlNext: skillzero@gmail.com
Message 2 of 3 in “Figuring out which patches have been applied”
  1. Jon SmirlOct 2, 2009
  2. Julian PhillipsOct 2, 2009
  3. skillzero@gmail.comOct 2, 2009

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.