I like this idea the best. Mike
> -----Original Message----- > From: edk2-devel [mailto:edk2-devel- > boun...@lists.01.org] On Behalf Of Leif Lindholm > Sent: Friday, December 15, 2017 5:12 AM > To: Evan Lloyd <evan.ll...@arm.com> > Cc: edk2-devel (edk2-devel@lists.01.org) <edk2- > de...@lists.01.org>; Ard Biesheuvel > <ard.biesheu...@linaro.org> > Subject: Re: [edk2] [staging/DynamicTables] What about > edk2-platforms. > > On Thu, Dec 14, 2017 at 06:38:14PM +0000, Evan Lloyd > wrote: > > We are about to submit a new (ACPI 6.2) version of > Sami's Dynamic Tables module. > > As suggested in previous threads, the aim is to > submit it to edk2-staging. > > To that end, following the instructions at > https://github.com/tianocore/edk2- > staging/blob/about/README > > (paragraph 4 a) "Maintainer sends patch email to > edk2-devel", we need to generate a patch. > > > > The problem is that the patch involves modules in > both edk2 and edk2-platforms. > > What is the best strategy to use for that scenario? > > Is there any plan to have an edk2-platforms-staging? > > If not, we could roll the bits of platforms into > edk2-staging, but that may engender problems later. > > Does anyone have any advice on how best to handle > this, please? > > As a third responder, I feel obliged to offer a third > opinion. > > My instinctive reaction is to set up a devel- > dynamictables branch in > edk2-platforms, that rebases periodically on master and > maintains > alignment as required with the edk2-staging branch. > > / > Leif > _______________________________________________ > 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
