public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yuwei Chen" <yuwei.chen@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"ayushdevel1325@gmail.com" <ayushdevel1325@gmail.com>
Cc: Michael Kubacki <mikuback@linux.microsoft.com>
Subject: Re: [edk2-devel] BaseTools: Current status of BaseTools/Source/Python
Date: Fri, 24 Jun 2022 02:02:50 +0000	[thread overview]
Message-ID: <MW5PR11MB5906E22AC6E852A8266A38B896B49@MW5PR11MB5906.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CA+Yfj7vmNZ1=7BWUD-WFOKCzcE9tu=hRNuSHShF=Fee2P6uZQw@mail.gmail.com>

Hi Ayush,

The migration is still working in progress. 
In order to ensure the normal use of users, the current bug fixes are still based on BaseTools in edk2. 
After all the migrations are completed, an official notification will be sent, and the developments and bug fixing works will be transferred to the edk2-basetools repo.

Thanks,
Christine (Yuwei)

> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Ayush
> Singh
> Sent: Saturday, June 11, 2022 11:31 PM
> To: edk2-devel-groups-io <devel@edk2.groups.io>
> Cc: Michael Kubacki <mikuback@linux.microsoft.com>
> Subject: [edk2-devel] BaseTools: Current status of BaseTools/Source/Python
> 
> Hello everyone,
> 
> I have been poking around the BaseTools to understand its implementation
> since I will have to add Rust build support as a part of my GSoC project. The
> `BaseTools/Source/Python` directory contains a README file that states that
> the folder was supposed to be removed from the repo on 202102.
> 
> It is still present in the repo, but more importantly, it still seems to be getting
> commits. Initially, I thought that maybe it was a mirror kind of situation but
> the commit history does not match, so I'm not sure.
> 
> Can anyone tell me what the current status of migration is, or if it has been
> canceled?
> 
> Yours Sincerely,
> Ayush Singh
> 
> [1] https://github.com/tianocore/edk2
> [2] https://github.com/tianocore/edk2-basetools
> 
> 
> 
> 


      reply	other threads:[~2022-06-24  2:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11 15:30 BaseTools: Current status of BaseTools/Source/Python Ayush Singh
2022-06-24  2:02 ` Yuwei Chen [this message]

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=MW5PR11MB5906E22AC6E852A8266A38B896B49@MW5PR11MB5906.namprd11.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