On Fri, May 11, 2018 at 01:29:47PM +0000, Evan Lloyd wrote:
>
>
> > -----Original Message-----
> > From: edk2-devel <[email protected]> On Behalf Of Leif
> > Lindholm
> > Sent: 09 May 2018 12:04
> > To: Sami Mujawar <[email protected]>
> > Cc: nd <[email protected]>; Arvind Chauhan <[email protected]>;
> > [email protected]; [email protected]; Stephanie Hughes-Fitt
> > <[email protected]>
> > Subject: Re: [edk2] [PATCH edk2-platforms v1 3/3][platforms/devel-
> > dynamictables] Update Readme.md to reflect ACPICA compiler update
> >
> ...
> > > -A patch ***'Modify hex AML C header file generation'***, to enable
> > > -this support has been submitted to the ACPICA source repository.
> > > -<https://lists.acpica.org/pipermail/devel/2018-March/001755.html>
> > > +A patch ***'[iASL: Enhance the -tc option (create AML hex file in
> > >
> > +C)](https://github.com/acpica/acpica/commit/f9a88a4c1cd020b6a5475d63
> > b
> > > +29626852a0b5f37)'***, to enable this support has been integrated to
> > > +the ACPICA source repository.
> >
> > Linux distributions tend to use dates to refer to what particular point a
> > version is based on, since snapshot updates are frequently
> > necessary.
>
> [[Evan Lloyd]] Whilst agreeing that a date would be helpful, I don't
> think that Linux usage is relevant. EDK II seems to go to some
> lengths to avoid Linux usage (e.g. CR LF).
Linux distributions are consumers of edk2 code in the form of
packaged builds of ArmVirtPkg and OvmfPkg.
> > In this case, that is 16 March 2018 - please mention that as well in the
> > message.
> [[Evan Lloyd]] Given the international nature of edk2-devel, I
> suggest there is a strong case for adopting ISO-8601 date format, so
> I'd prefer 2018-03-16.
Yes please.
/
Leif
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.01.org/mailman/listinfo/edk2-devel
