From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"rebecca@bsdio.com" <rebecca@bsdio.com>,
Gerd Hoffmann <kraxel@redhat.com>
Cc: "Marvin Häuser" <mhaeuser@posteo.de>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [edk2-platforms] Enable GitHub PR, protected branches, and 'push' label
Date: Fri, 17 Mar 2023 15:27:01 +0000 [thread overview]
Message-ID: <CO1PR11MB4929A51976EA879A42863B50D2BD9@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <312a8fbb-1eab-6cf4-b68a-62598b15f700@bsdio.com>
The full lists.01.org history was imported into groups.io.
Stephano did a great job working with groups.io to make that happen.
Mike
> -----Original Message-----
> From: Rebecca Cran <rebecca@bsdio.com>
> Sent: Friday, March 17, 2023 3:58 AM
> To: Gerd Hoffmann <kraxel@redhat.com>; devel@edk2.groups.io
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Marvin Häuser <mhaeuser@posteo.de>
> Subject: Re: [edk2-devel] [edk2-platforms] Enable GitHub PR, protected branches, and 'push' label
>
> Sorry, it might be the sourceforge mailing list that got lost, not
> lists.01.org. I was wanting to see the review of the following commit,
> but Google isn't finding anything:
>
>
> commit a61331e8b78ba264f0ccd011b6dc5b9e809730a5
> Author: Liming Gao <liming.gao@intel.com>
> Date: Mon Aug 22 14:32:23 2016 +0800
>
> BaseTools GnuMakefile: Update GCC Flags to the specific one with
> BUILD_ prefix
>
>
>
> On 3/17/23 4:48 AM, Rebecca Cran wrote:
> > Talking about mailing lists, I'm still disappointed that we lost so
> > much history of discussion and reviews around the project when the
> > edk2-devel archive at lists.01.org was deleted.
> >
> > I've sometimes wanted to go back and take a look at the review history
> > of a certain commit only to find it's been lost.
> >
> >
next prev parent reply other threads:[~2023-03-17 15:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 20:02 [edk2-platforms] Enable GitHub PR, protected branches, and 'push' label Michael D Kinney
2023-03-15 22:24 ` [edk2-devel] " Marvin Häuser
2023-03-15 22:34 ` Michael D Kinney
2023-03-16 19:54 ` Marvin Häuser
2023-03-16 19:59 ` Rebecca Cran
2023-03-17 9:33 ` Gerd Hoffmann
2023-03-17 10:36 ` Rebecca Cran
2023-03-17 10:48 ` Rebecca Cran
[not found] ` <174D2F2BAAB7643C.10271@groups.io>
2023-03-17 10:57 ` Rebecca Cran
2023-03-17 15:27 ` Michael D Kinney [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-17 12:32 Marvin Häuser
2023-03-17 12:57 ` Rebecca Cran
2023-03-17 13:44 ` Gerd Hoffmann
2023-03-17 14:08 ` Marvin Häuser
2023-03-17 14:20 ` Rebecca Cran
2023-03-17 15:37 ` Michael D Kinney
2023-03-17 14:22 ` Rebecca Cran
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=CO1PR11MB4929A51976EA879A42863B50D2BD9@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