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

Re: retrieving a diff from git

From
CJChristian Jaeger <christian@jaeger.mine.nu>
Date
Oct 15, 2008, 10:12 UTC
Message-ID
<48F5C218.3080807@jaeger.mine.nu>
In-Reply-To
<20081014172048.GW22427@vanheusden.com>
Folkert van Heusden wrote:
Show 13 quoted lines
>> Well, you can of course just click on "commitdiff" (and "raw" afterwords)
>> for every commit,
>>     
>
> Hmmm the outcome does not apply cleanly to 2.6.27.
>
>   
>> but ... Have you considered using Git for that?
>>     
>
> and check out the whole tree using Git? I did consider but then I would
> not have all bells and whistles to generate a Debian kernel package.
>

I'm tempted to think that you should move (merge / cherry-pick or rebase) the relevant changes onto 2.6.27 using Git, and then take the diff from there (on the theory that Git could reduce the number of conflicts that you would have to resolve manually, although I'm not sure how much this is the case); the resulting diff will then apply cleanly to a 2.6.27 tarball without using Git.

Christian.
Previous: Matthieu Moy
Message 6 of 6 in “retrieving a diff from git”
  1. Folkert van HeusdenOct 14, 2008
  2. Alex RiesenOct 14, 2008
  3. Folkert van HeusdenOct 14, 2008
  4. Alex RiesenOct 14, 2008
  5. Matthieu MoyOct 14, 2008
  6. Christian JaegerOct 15, 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.