On 01/16/16 15:25, Ard Biesheuvel wrote: > On 15 January 2016 at 22:14, Jarlstrom, Laurie > <laurie.jarlst...@intel.com> wrote: >> To: EDK II Community >> >> This message is an update on the transition from SourceForge to GitHub for >> EDK II development. The schedule is currently targeting the last week of >> January or the first week of February to perform the transition. The >> transition process should only take one to two days to complete. A >> notification message will be sent the week prior to the actual dates that >> the repositories will be impacted. This should provide adequate >> notification for the scheduled down time. >> As part of this transition some documentation and process changes have been >> required. The updated process as well as other GitHub specific information >> can be found on the tianocore Wiki at the link provided below. Feedback on >> this documentation is welcome and needed to make sure the transition is as >> smooth as possible. >> >> https://github.com/tianocore/tianocore.github.io/wiki/SourceForge-to-Github-Quick-Start >> >> Please post any comments or questions related to this transition to the >> edk2-devel mailing list or reply to the email message. >> > > Hello, > > Thanks for getting all of this set up. > > Regarding the following line > > 'Commits should build / boot if possible to support use of bisect' > > could we make that a bit stronger please? Breaking bisect is really > not ok, and it usually does not take that much extra work to avoid it, > as long as you are aware of it. Given that many people are new to Git, > presenting it as an opt-in feature like this does not send the right > message imo. > > In fact, having some guidelines about how to avoid breaking bisect > could be helpful, especially that something like adding some temporary > code in an early patch only to remove it again at the end of the > series is perfectly ok, and highly preferred over losing > bisectability. Not everybody might expect that.
I agree completely. Minimally the one package that the developer uses for developing the series must build at each stage in the series, with at least the developer's preferred toolchain and build flags. Thanks Laszlo > > Thanks, > Ard. > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel > _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
