-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Somebody in the thread at some point said:
| Mirko Vogt wrote:
|> Is there a location where all the atomar patches related to kernel
|> 2.6.28 / Openmoko are stored?
|| We stopped keeping patches in that way quite a while ago already.
| So if you're looking for what Openmoko did, just checking out the
| tree is indeed your principal option.
|| It shouldn't be too bad, since most of our code is actually in new
| files, e.g., complete drivers or machine/platform-specific stuff.
| Fixes to code that's already in mainline are usually submitted
| upstream right away, so before long they should disappear from
| "our" set of changes.
Right, we are starting to push chunks of our stuff upstream as well.
What we have is incremental patcheset now, but we do have a history.
You can use git diff to arrive at a flat diff set, depending on what
you're trying to do (ie, see what we alter in mainline as opposed to
what drivers we add) that can be enlightening.
There's also still the old patchset upleveled for 2.6.28 in
mokopatches-tracking branch in git, but that's "half the story" now.
http://git.openmoko.org/?p=kernel.git;a=shortlog;h=mokopatches-tracking
Maybe explain what you're trying to do with what you're looking for and
there is another way to come at it.
- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAklTuYoACgkQOjLpvpq7dMqeewCfboBIay9umZmdRj8Ti4DFS9va
ukgAn0arfypUdSNNs/kZvAJRA+pl/rDs
=f+Gm
-----END PGP SIGNATURE-----