On 03/06/2015 13:57, Laszlo Ersek wrote: >> > >> > Bisectability would be extremely painful, because bisection on the >> > master repository would leave you at the single huge commit where you >> > atomically update all subpackages. You would have no clue of how to >> > bisect _within_ that atomic update, in fact in some case you cannot. > Thanks for the education. > > Although bisectability has not been treated as a primary goal across all > of edk2 (unfortunately!), in OvmfPkg we always consider it a first class > goal -- that's how one find bugs and supports users --, and the project > in general should move towards bisectability (and more focused, fine > grained patches), not away from them. > > In fact the scenario you described is the original BaseTools situation > all over. Frequently when a BaseTools sync happened, stuff would break, > and users would be left with an unbisectable, multi-KLOC BaseTools patch > to eyeball.
On one hand it would be better because master repo updates would be more frequent. On the other hand it would much much worse because BaseTools updates only updated one repo, while here one update could plausibly touch all of IntelFrameworkPkg, OvmfPkg, PcAtChipsetPkg and UefiCpuPkg or something like that. Paolo ------------------------------------------------------------------------------ _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel