public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Vivian Shi (石丽) via groups.io" <VivianShi=ami.com@groups.io>
To: "Kasbekar, Saloni" <saloni.kasbekar@intel.com>,
	Sivaraman Nainar <sivaramann@ami.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Dhanaraj V" <vdhanaraj@ami.com>,
	"Clark-williams, Zachary" <zachary.clark-williams@intel.com>,
	"Hunter Qi (戚硕)" <HunterQi@ami.com>,
	"Ivan Gu (顾鸣磊)" <IvanGu@ami.com>,
	"Joybird Gu (顾哲鹤)" <JoybirdGu@ami.com>
Subject: Re: [edk2-devel] reg: HTTP Proxy Support
Date: Tue, 19 Mar 2024 07:00:50 +0000	[thread overview]
Message-ID: <DS7PR10MB508598E9E88F9DB1A3664EE5AD2C2@DS7PR10MB5085.namprd10.prod.outlook.com> (raw)
In-Reply-To: <DS7PR10MB508597741836357DB29A5536AD7D2@DS7PR10MB5085.namprd10.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 4171 bytes --]

Hi Saloni,

Sorry for the drop in.
Is there any schedule for pull in the HTTP Proxy changes from edk2-staging to edk2?

Thanks a lot!
Best Regards
Vivian Shi

American Megatrends Information Technology (Kunshan) Co., Ltd.

Tel: +86-512-57360204 #259

From: Vivian Shi (石丽)
Sent: Tuesday, January 30, 2024 9:19 AM
To: Kasbekar, Saloni <saloni.kasbekar@intel.com>; Sivaraman Nainar <sivaramann@ami.com>; devel@edk2.groups.io
Cc: Dhanaraj V <vdhanaraj@ami.com>; Clark-williams, Zachary <zachary.clark-williams@intel.com>; Hunter Qi (戚硕) <HunterQi@ami.com>; Ivan Gu (顾鸣磊) <IvanGu@ami.com>; Joybird Gu (顾哲鹤) <JoybirdGu@ami.com>
Subject: RE: [EXTERNAL] RE: reg: HTTP Proxy Support

Cc more.

Thanks a lot!
Best Regards
Vivian Shi

American Megatrends Information Technology (Kunshan) Co., Ltd.

Tel: +86-512-57360204 #259

From: Kasbekar, Saloni <saloni.kasbekar@intel.com<mailto:saloni.kasbekar@intel.com>>
Sent: Tuesday, January 30, 2024 2:03 AM
To: Sivaraman Nainar <sivaramann@ami.com<mailto:sivaramann@ami.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Cc: Dhanaraj V <vdhanaraj@ami.com<mailto:vdhanaraj@ami.com>>; Vivian Shi (石丽) <VivianShi@ami.com<mailto:VivianShi@ami.com>>; Clark-williams, Zachary <zachary.clark-williams@intel.com<mailto:zachary.clark-williams@intel.com>>
Subject: [EXTERNAL] RE: reg: HTTP Proxy Support


**CAUTION: The e-mail below is from an external source. Please exercise caution before opening attachments, clicking links, or following guidance.**
Hi Siva,

The changes for HTTP Proxy in edk2-staging are part of the code first process since they are dependent on corresponding changes in the UEFI spec.
As a part of the code first process once the next version of UEFI spec is released, we can pull in the changes from edk2-staging to edk2.

Thanks,
Saloni

From: Sivaraman Nainar <sivaramann@ami.com<mailto:sivaramann@ami.com>>
Sent: Sunday, January 28, 2024 9:59 PM
To: Kasbekar, Saloni <saloni.kasbekar@intel.com<mailto:saloni.kasbekar@intel.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Cc: Dhanaraj V <vdhanaraj@ami.com<mailto:vdhanaraj@ami.com>>; Vivian Shi (石丽) <VivianShi@ami.com<mailto:VivianShi@ami.com>>; Clark-williams, Zachary <zachary.clark-williams@intel.com<mailto:zachary.clark-williams@intel.com>>
Subject: reg: HTTP Proxy Support

Hello Saloni,

Update Code First markdown file for specification text changes ・ tianocore/edk2-staging@b8816aa ・ GitHub<https://github.com/tianocore/edk2-staging/commit/b8816aaf12c33efb1e1959e77383f633fed47a69#diff-a758f76d21d7cd0728fcc8e1c6fdcba6aa0022754cf2621db66a5c9c09173c29>

This branch has support for HTTP Proxy. Do we have any plan to bring to to master tree?

Thanks
Siva
-The information contained in this message may be confidential and proprietary to American Megatrends (AMI). This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.
-The information contained in this message may be confidential and proprietary to American Megatrends (AMI). This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#116941): https://edk2.groups.io/g/devel/message/116941
Mute This Topic: https://groups.io/mt/104026673/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #2: Type: text/html, Size: 13707 bytes --]

  reply	other threads:[~2024-03-20 13:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29  5:58 [edk2-devel] reg: HTTP Proxy Support Sivaraman Nainar via groups.io
2024-01-29 18:02 ` Saloni Kasbekar
2024-01-30  1:19   ` Vivian Shi (石丽) via groups.io
2024-03-19  7:00     ` Vivian Shi (石丽) via groups.io [this message]
2024-03-19 21:30       ` Saloni Kasbekar

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=DS7PR10MB508598E9E88F9DB1A3664EE5AD2C2@DS7PR10MB5085.namprd10.prod.outlook.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