From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: linuxppc-embedded@ozlabs.org
Subject: how to get individual patches
Date: Wed, 28 Jun 2006 03:49:28 -0400 [thread overview]
Message-ID: <44A23488.7030606@dlasys.net> (raw)
In-Reply-To: <20060627212448.7d048b7a@White64>
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.
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys.net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein
next prev parent reply other threads:[~2006-06-28 7:49 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 ` David H. Lynch Jr. [this message]
2006-06-28 8:32 ` how to get individual patches Alex Zeffertt
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=44A23488.7030606@dlasys.net \
--to=dhlii@dlasys.net \
--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 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).