git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Jaeger <christian@jaeger.mine.nu>
To: Folkert van Heusden <folkert@vanheusden.com>
Cc: Alex Riesen <raa.lkml@gmail.com>, git@vger.kernel.org
Subject: Re: retrieving a diff from git
Date: Wed, 15 Oct 2008 12:12:40 +0200	[thread overview]
Message-ID: <48F5C218.3080807@jaeger.mine.nu> (raw)
In-Reply-To: <20081014172048.GW22427@vanheusden.com>

Folkert van Heusden wrote:
>> 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.

      parent reply	other threads:[~2008-10-15 10:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14 14:51 retrieving a diff from git Folkert van Heusden
2008-10-14 17:01 ` Alex Riesen
2008-10-14 17:20   ` Folkert van Heusden
2008-10-14 17:29     ` Alex Riesen
2008-10-14 17:56     ` Matthieu Moy
2008-10-15 10:12     ` Christian Jaeger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48F5C218.3080807@jaeger.mine.nu \
    --to=christian@jaeger.mine.nu \
    --cc=folkert@vanheusden.com \
    --cc=git@vger.kernel.org \
    --cc=raa.lkml@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).