From: Alex Zeffertt <ajz@cambridgebroadband.com>
To: dhlii@comcast.net, linuxppc-embedded@ozlabs.org
Subject: Re: how to get individual patches
Date: Wed, 28 Jun 2006 09:32:26 +0100 [thread overview]
Message-ID: <44A23E9A.50004@cambridgebroadband.com> (raw)
In-Reply-To: <44A23488.7030606@dlasys.net>
David H. Lynch Jr. wrote:
> The bsp I am working on works with 2.6.16.21 but fails with 2.6.17.
>
> How can I find the individual patches that make up the transition
> from 2.6.16.21 to 2.6.17 ?
>
> I guess I can use interdiff to create single patch to go from
> 2.6.16.21 to 2.6.17 but I am really looking to get all the individual
> patches so I can try to isolate exactly
> what is giving me trouble.
>
For diffs of individual files between official kernel releases you can
use
http://www.linuxhq.com/kernel/
It's really good!
Alex
next prev parent reply other threads:[~2006-06-28 8:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 18:38 Lite5200 MTD partitions in 2.6 build Rowan, Chad
2006-06-27 19:24 ` White
2006-06-28 7:49 ` how to get individual patches David H. Lynch Jr.
2006-06-28 8:32 ` Alex Zeffertt [this message]
2006-06-28 16:22 ` David H. Lynch Jr.
2006-06-28 9:09 ` Grant Likely
2006-06-28 16:18 ` David H. Lynch Jr.
2006-07-14 18:13 ` David H. Lynch Jr.
2006-07-14 18:22 ` Grant Likely
2006-07-17 3:46 ` David H. Lynch Jr.
2006-07-17 5:30 ` Grant Likely
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=44A23E9A.50004@cambridgebroadband.com \
--to=ajz@cambridgebroadband.com \
--cc=dhlii@comcast.net \
--cc=linuxppc-embedded@ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.