I agree with Dale... This is not a new problem and has already been discussed (in threads I can dig up if you really want them and verbally) we should optimize for the 95% case where we are not doing gaia+gecko patches...
- james ----- Original Message ----- From: "Dale Harvey" <[email protected]> To: "Gary Kwong" <[email protected]> Cc: "Fabrice Desré" <[email protected]>, "Ed Morley" <[email protected]>, "James Lal" <[email protected]>, "dev-b2g" <[email protected]>, "Sheriffs" <[email protected]>, [email protected] Sent: Thursday, November 7, 2013 3:12:05 PM Subject: Re: [b2g] Move Gaia to the same repository as Gecko (was Re: Workflow for landing gecko patches that require changes to gaia tests) While I really hate the workflow of having to bisect problems that may be anywhere between 2 seperate repositories Putting gaia inside m-c doesnt seem like a scalable solution, should we be putting gonk / the rest of android in there too? I feel like in m-c I already see problems related to trying to chuck everything in the same basket, shouldnt we be looking to better uncouple projects (like repo per app in gaia :)) and have a better understanding of tools like repo or other tools for handing multiple repositories (but not submodules) On 7 November 2013 13:22, Gary Kwong <[email protected]> wrote: > The other alternative to make it painless to land gecko+gaia atomic >> changes is of course to move gaia to the same repo as gecko, and make >> the github repo a readonly mirror of gaia-hg. I'm sure I will be very >> popular with this proposal in gaia circles ;) >> > > This is interesting. More consolidation of repos - releng might have some > ideas? > > If this seems like a possible way forward, perhaps a bug could be filed? > > -Gary > _______________________________________________ > 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
