public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: stephano <stephano.cetola@linux.intel.com>
To: "Gao, Liming" <liming.gao@intel.com>,
	"KarunakarPoosapalli@Dell.com" <KarunakarPoosapalli@Dell.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"lersek@redhat.com" <lersek@redhat.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Sumanth.Vidyadhara@dell.com" <Sumanth.Vidyadhara@dell.com>,
	"Shekar.Babu.S@dell.com" <Shekar.Babu.S@dell.com>,
	"Sriramkumar.Raju@dell.com" <Sriramkumar.Raju@dell.com>,
	"Anand.Joshi@dell.com" <Anand.Joshi@dell.com>
Subject: Re: Conditional Compilation support in INF file
Date: Thu, 31 Jan 2019 08:26:50 -0800	[thread overview]
Message-ID: <a6a90ff0-2c6a-2363-5db6-f2870fabdf99@linux.intel.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3D4146@SHSMSX104.ccr.corp.intel.com>

On 1/30/2019 10:56 PM, Gao, Liming wrote:
> Karunakar:
>    There is one BZ https://bugzilla.tianocore.org/show_bug.cgi?id=1446 on Feature Flag expression in INF. INF spec has listed the syntax for it. But, BaseTools doesn't support it now. If you have the similar request, please add the information in BZ (including the usage model and expected edk2 release). And, stephano are working on Public Design and Bug Scrub Meetings. Then, we can talk the fix plan in public bug scrub meeting.
> 

Design and Community Bug Triage meetings are indeed in the works.

I should have notifications out to the mailing list soon. I am traveling 
to FOSDEM today, so I should have an email out by the weekend.

Cheers,
Stephano


  reply	other threads:[~2019-01-31 16:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09  6:55 Conditional Compilation support in INF file KarunakarPoosapalli
2019-01-09 11:00 ` Laszlo Ersek
2019-01-09 12:42   ` Gao, Liming
2019-01-09 14:37     ` Laszlo Ersek
2019-01-10  6:03     ` KarunakarPoosapalli
2019-01-10 12:54       ` Laszlo Ersek
2019-01-10 15:48         ` Gao, Liming
2019-01-10 16:53           ` Kinney, Michael D
2019-01-11  6:33             ` KarunakarPoosapalli
2019-01-11 18:54               ` Kinney, Michael D
2019-01-15 15:10                 ` Gao, Liming
2019-01-28  7:50                   ` KarunakarPoosapalli
2019-01-28  8:36                   ` KarunakarPoosapalli
2019-01-31  6:56                     ` Gao, Liming
2019-01-31 16:26                       ` stephano [this message]
2019-02-01 10:52                         ` KarunakarPoosapalli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a6a90ff0-2c6a-2363-5db6-f2870fabdf99@linux.intel.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox