From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"ayushdevel1325@gmail.com" <ayushdevel1325@gmail.com>
Cc: "mikuback@linux.microsoft.com" <mikuback@linux.microsoft.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Gaibusab, Jabeena B" <jabeena.b.gaibusab@intel.com>
Subject: Re: [edk2-devel] Proposal to move Rust std work to a Repository under Tianocore
Date: Mon, 1 Aug 2022 19:08:17 +0000 [thread overview]
Message-ID: <CO1PR11MB4929E96BEC1EBD70804897FCD29A9@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <0405e546-04b0-1bd8-183a-e62691666286@gmail.com>
Hi Ayush,
Since this is a fork of the rust project, I would
recommend following the branch naming convention used
by other PRs in the rust project.
Thanks,
Mike
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Ayush Singh
> Sent: Monday, August 1, 2022 12:01 PM
> To: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>
> Cc: mikuback@linux.microsoft.com; Yao, Jiewen <jiewen.yao@intel.com>; Gaibusab, Jabeena B <jabeena.b.gaibusab@intel.com>
> Subject: Re: [edk2-devel] Proposal to move Rust std work to a Repository under Tianocore
>
> Hi Mike. What should be the naming scheme of the branch/s? I think you
> already had some in mind to handle the development workflow.
>
> Ayush Singh
>
>
> On 8/1/22 23:43, Michael D Kinney wrote:
> > Hi Ayush,
> >
> > I have created a fork in tianocore
> >
> > https://github.com/tianocore/rust
> >
> > I have added you and the EDK II Maintainers as collaborators on this repo.
> >
> > Please let me know if any permission changes need to be made for you
> > to migrate your work into this repository.
> >
> > Thanks,
> >
> > Mike
> >
> >> -----Original Message-----
> >> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Ayush Singh
> >> Sent: Monday, August 1, 2022 10:02 AM
> >> To: devel@edk2.groups.io
> >> Cc: Kinney, Michael D <michael.d.kinney@intel.com>; mikuback@linux.microsoft.com; Yao, Jiewen <jiewen.yao@intel.com>;
> Gaibusab,
> >> Jabeena B <jabeena.b.gaibusab@intel.com>
> >> Subject: [edk2-devel] Proposal to move Rust std work to a Repository under Tianocore
> >>
> >> Hello everyone. In the previous email thread [1], I discussed the
> >> proposal to move Rust std work to edk2-staging and mentioned its
> >> potential problems. After some discussion with mentors, we arrived at
> >> the conclusion to have a rustlang [2] fork under the Tianocore
> >> organization, and move all the std related work there. We can then open
> >> a PR upstream from there, while allowing PRs in this repository. This
> >> should help provide an easier and streamlined way for people to
> >> experiment and work on this project while it is in the process of being
> >> merged upstream.
> >>
> >>
> >> For a status update about tests:
> >>
> >> - passed: 12797
> >>
> >> - failed: 40
> >>
> >> - ignored: 375
> >>
> >>
> >> Yours Sincerely,
> >>
> >> Ayush Singh
> >>
> >>
> >> [1]: https://edk2.groups.io/g/devel/message/91989
> >>
> >> [2]: https://github.com/rust-lang/rust
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
> >
> >
>
>
>
>
prev parent reply other threads:[~2022-08-01 19:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 17:02 Proposal to move Rust std work to a Repository under Tianocore Ayush Singh
2022-08-01 17:26 ` [edk2-devel] " Pedro Falcato
2022-08-01 17:39 ` Ayush Singh
2022-08-01 19:06 ` Pedro Falcato
2022-08-01 19:14 ` Michael D Kinney
2022-08-01 19:36 ` Ayush Singh
2022-08-01 17:50 ` Ayush Singh
2022-08-01 18:07 ` Yao, Jiewen
2022-08-01 18:55 ` Ayush Singh
2022-08-01 21:16 ` Leonardo Garcia
2022-08-01 18:13 ` Michael D Kinney
2022-08-01 19:01 ` Ayush Singh
2022-08-01 19:08 ` Michael D Kinney [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=CO1PR11MB4929E96BEC1EBD70804897FCD29A9@CO1PR11MB4929.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