public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, philmd@redhat.com, rebecca@bsdio.com
Cc: Ray Ni <ray.ni@intel.com>, Leif Lindholm <leif@nuviainc.com>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	Andrew Fish <afish@apple.com>
Subject: Re: [edk2-devel] [PATCH 1/1] Update mailing list links from lists.01.org to groups.io
Date: Tue, 5 May 2020 18:34:11 +0200	[thread overview]
Message-ID: <417c08c7-b4e9-9e3e-007d-415b1f9e0659@redhat.com> (raw)
In-Reply-To: <c3c157bd-7db0-af1f-6848-be8fd7ae4923@redhat.com>

On 05/04/20 13:48, Philippe Mathieu-Daudé wrote:
> On 4/30/20 11:06 PM, Rebecca Cran wrote:
>> I only updated links to the top-level mailing list, not any links to
>> individual messages.
>>
>> Signed-off-by: Rebecca Cran <rebecca@bsdio.com>
>> ---
>>   HardFeatureFreeze.md                                          | 2 +-
>>   ...unkempt-git-guide-for-edk2-contributors-and-maintainers.md | 2 +-
>>   Member-FAQ.md                                                 | 4 ++--
>>   SoftFeatureFreeze.md                                          | 2 +-
>>   4 files changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/HardFeatureFreeze.md b/HardFeatureFreeze.md
>> index dae9f664b5d9..e0334f69ed7e 100644
>> --- a/HardFeatureFreeze.md
>> +++ b/HardFeatureFreeze.md
>> @@ -10,7 +10,7 @@
>> freeze](https://wiki.qemu.org/Planning/HardFeatureFreeze)).
>>   The proposed schedule for the active development cycle is shown in
>> the [EDK II
>>   Release Planning](EDK-II-Release-Planning) article. Shortly before
>> the hard
>>   feature freeze, an announcement email is sent to the
>> -[edk2-devel](https://lists.01.org/mailman/listinfo/edk2-devel)
>> mailing list.
>> +[edk2-devel](https://edk2.groups.io/g/devel) mailing list.
>>   The announcement is posted by one of the maintainers that are listed in
>>  
>> [Maintainers.txt](https://github.com/tianocore/edk2/blob/master/Maintainers.txt),
>>
>>   in section `EDK II Releases`.
>> diff --git
>> a/Laszlo's-unkempt-git-guide-for-edk2-contributors-and-maintainers.md
>> b/Laszlo's-unkempt-git-guide-for-edk2-contributors-and-maintainers.md
>> index 3469ef7b1845..6f85c782a710 100644
>> --- a/Laszlo's-unkempt-git-guide-for-edk2-contributors-and-maintainers.md
>> +++ b/Laszlo's-unkempt-git-guide-for-edk2-contributors-and-maintainers.md
>> @@ -80,7 +80,7 @@ Contributor workflow
>>        git config notes.rewriteRef       refs/notes/commits
>>        git config sendemail.chainreplyto false
>>        git config sendemail.thread       true
>> -     git config sendemail.to           edk2-devel@lists.01.org
>> +     git config sendemail.to           devel@edk2.groups.io
>>        ```
>>     6.   <a name="contrib-06" href="#contrib-06">&sect;</a>
>> diff --git a/Member-FAQ.md b/Member-FAQ.md
>> index f3e5798f23ae..f277744ff6ce 100644
>> --- a/Member-FAQ.md
>> +++ b/Member-FAQ.md
>> @@ -7,6 +7,6 @@ TianoCore has accumulated a lot of information over
>> the years. We keep several F
>>   * [[Terms and Acronyms|Acronyms and Glossary]]
>>   * [[EDK II Documents]]
>>   -If you have a question and cannot find the answer, please try the
>> [EDK II developer e-mail
>> list](https://github.com/tianocore/tianocore.github.io/wiki/edk2-devel).
>> You can also [search the e-mail list
>> archive](https://lists.01.org/pipermail/edk2-devel/) for questions
>> already asked in email.
>> +If you have a question and cannot find the answer, please try the
>> [EDK II developer e-mail
>> list](https://github.com/tianocore/tianocore.github.io/wiki/edk2-devel).
>> You can also [search the e-mail list
>> archive](https://edk2.groups.io/g/devel) for questions already asked
>> in email.
>>   -_Note that e-mails prior to September 2015 are on a [sourceforge
>> archive](https://sourceforge.net/p/edk2/mailman/edk2-devel/)._
>> \ No newline at end of file
>> +_Note that e-mails prior to September 2015 are on a [sourceforge
>> archive](https://sourceforge.net/p/edk2/mailman/edk2-devel/)._
>> diff --git a/SoftFeatureFreeze.md b/SoftFeatureFreeze.md
>> index 9047a73c1d69..7a0f40bbeaf4 100644
>> --- a/SoftFeatureFreeze.md
>> +++ b/SoftFeatureFreeze.md
>> @@ -46,7 +46,7 @@
>> freeze](https://wiki.qemu.org/Planning/SoftFeatureFreeze).)
>>   The proposed schedule for the active development cycle is shown in
>> the [EDK II
>>   Release Planning](EDK-II-Release-Planning) article. Shortly before
>> the soft
>>   feature freeze, an announcement email is sent to the
>> -[edk2-devel](https://lists.01.org/mailman/listinfo/edk2-devel)
>> mailing list.
>> +[edk2-devel](https://edk2.groups.io/g/devel) mailing list.
>>   The announcement is posted by one of the maintainers that are listed in
>>  
>> [Maintainers.txt](https://github.com/tianocore/edk2/blob/master/Maintainers.txt),
>>
>>   in section `EDK II Releases`.
>>
> 
> Reviewed-by: Philippe Mathieu-Daude <philmd@redhat.com>

Reviewed-by: Laszlo Ersek <lersek@redhat.com>

edk2-wiki commit ae81cb24e5ba.

Thanks!
Laszlo


  reply	other threads:[~2020-05-05 16:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 21:06 [PATCH 1/1] Update mailing list links from lists.01.org to groups.io Rebecca Cran
2020-05-04 11:48 ` [edk2-devel] " Philippe Mathieu-Daudé
2020-05-05 16:34   ` Laszlo Ersek [this message]
     [not found] <160AB4F99F643457.16331@groups.io>
2020-04-30 21:21 ` 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=417c08c7-b4e9-9e3e-007d-415b1f9e0659@redhat.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