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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
