We have infrastructure to deal with this in the form of an automated patching system for smaller patches that we cannot upstream.
https://github.com/mozilla-b2g/gonk-patches Contains the relevant code and the current set of patches. The patching script is invoked as a part of build.sh. John ----- Original Message ----- From: "Jed Davis" <[email protected]> To: [email protected] Sent: Friday, May 31, 2013 11:03:39 AM Subject: [b2g] B2G-specific changes to Android repositories What are we planning to do with changes we make to the various Android repositories we're using? Ideally we'd like to upstream changes where possible, but some of them may not be of interest upstream, and/or we'd want to be able to build with them sooner than the upstream would accept them, and/or we might need to backport them anyway. Alternately, there exists gonk-patches, which works well enough technically, but my understanding is that we're trying to avoid using it where possible. So (at least in some cases) we'd need to fork things, and create our own branches on the Mozilla project's mirrors and push to them, but I don't know what the process for accomplishing that is, or even if one exists. Specifically, I don't know what I should be doing to make progress on bug 870639, which is blocking a lot of my profiling work from being able to be landed; but, in general, this seems unlikely to be the last issue of this form that we encounter. --Jed _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
