On Wed, Jun 01, 2011 at 10:33:27PM +0200, Zygmunt Krynicki wrote:
One of the things it does not capture currently is kernel configuration. Assuming you can cat /proc/config it would be easy to capture that as well but I would like to know what others think.
James has rightly pointed out that this will be available under /boot, right?
- What patches were applied on top of it (A URL to the patchset, maybe?)TBD, it's hard to say what those patches were. I would actually like a different solution, have the tree with pre-applied patches (so that we can still pinpoint the tree from git repo) and have a informative description of patches that were applied for other reasons. This would allow us to compare results of tests with and without a specific kernel patch (easy and interesting) withuot resorting to git bisections.
Well, the reason I asked for this was because I had the probably erroneous conception that we would have patches applied to the kernel that would not be committed to git. I have since reflected that John's tree, for instance, already includes any the packaging-related and SAUCE patches, so it's not immediately necessary.
However, thinking a bit further, it would be nice to have a reference to both the final branch (which the package was generated from) and the original, sans-packaging branch which the packaging branch added to. However, does this separation exist for all hwpacks? Do Landing Teams maintain separate packaging branches, or do you, John?