public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Rebecca Cran <rebecca@bluestop.org>
Cc: "Gao, Liming" <liming.gao@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [PATCH] Fix links in Maintainers.txt and remove slow, outdated sourceforge git mirror
Date: Tue, 26 Feb 2019 13:28:52 +0100	[thread overview]
Message-ID: <6800a51b-fa21-f325-bbc1-d17e3c8b62e2@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3E7718@SHSMSX104.ccr.corp.intel.com>

Rebecca,

On 02/26/19 00:56, Gao, Liming wrote:
> Yes. This is a bug fix. I agree to push it for Q1 release. 
> 
>> -----Original Message-----
>> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
>> Laszlo Ersek
>> Sent: Tuesday, February 26, 2019 3:36 AM
>> To: Gao, Liming <liming.gao@intel.com>; Rebecca Cran
>> <rebecca@bluestop.org>; edk2-devel@lists.01.org
>> Cc: Kinney, Michael D <michael.d.kinney@intel.com>
>> Subject: Re: [edk2] [PATCH] Fix links in Maintainers.txt and remove slow,
>> outdated sourceforge git mirror
>>
>> On 02/25/19 14:36, Gao, Liming wrote:
>>> I can't clone edk2 code from http://git.code.sf.net/p/tianocore/edk2.
>> Seemly, it doesn't work. So, I agree to remove it.
>>>
>>> Reviewed-by: Liming Gao <liming.gao@intel.com>
>>
>> Do we consider this a bugfix, suitable to be pushed during the soft
>> feature freeze?
>>
>> I suggest that we do.

I've tried applying this patch, and found two issues.

First, you didn't add:

Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Rebecca Cran <rebecca@bluestop.org>

Second, this patch is based on a very outdated state of the edk2 tree. I
have to apply it on top of commit 2d4fd226da42 ("BaseTools GenFw: Fix
XCODE5 build issue", 2019-01-15); otherwise it doesn't apply. It runs
into a conflict with commit 1f7b74831544 ("Maintainers.txt: Update mail
address", 2019-01-15).

I could fix issue #2 with a rebase myself; however, issue #1 has to be
fixed by you. Please post a v3, addressing both issues, and also picking
up the feedback tags that you received in this thread (from Liming and
myself).

Thanks,
Laszlo


>>>> -----Original Message-----
>>>> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
>> Laszlo Ersek
>>>> Sent: Monday, February 25, 2019 6:07 PM
>>>> To: Rebecca Cran <rebecca@bluestop.org>; edk2-devel@lists.01.org
>>>> Cc: Kinney, Michael D <michael.d.kinney@intel.com>
>>>> Subject: Re: [edk2] [PATCH] Fix links in Maintainers.txt and remove slow,
>> outdated sourceforge git mirror
>>>>
>>>> On 02/23/19 06:18, Rebecca Cran via edk2-devel wrote:
>>>>> ---
>>>>>  Maintainers.txt | 7 +++----
>>>>>  1 file changed, 3 insertions(+), 4 deletions(-)
>>>>>
>>>>> diff --git a/Maintainers.txt b/Maintainers.txt
>>>>> index 7f1061d6c1..d9d3d840c5 100644
>>>>> --- a/Maintainers.txt
>>>>> +++ b/Maintainers.txt
>>>>> @@ -31,11 +31,10 @@ Descriptions of section entries:
>>>>>
>>>>>  EDK II
>>>>>  ------
>>>>> -W: http://www.tianocore.org/edk2/
>>>>> -L: https://lists.sourceforge.net/lists/listinfo/edk2-devel
>>>>> +W: https://github.com/tianocore/tianocore.github.io/wiki/EDK-II
>>>>> +L: https://lists.01.org/mailman/listinfo/edk2-devel
>>>>>  T: git - https://github.com/tianocore/edk2.git
>>>>>  T: git (mirror) - https://bitbucket.org/tianocore/edk2.git
>>>>> -T: git (mirror) - http://git.code.sf.net/p/tianocore/edk2
>>>>>  T: svn (read-only, deprecated) -
>> https://svn.code.sf.net/p/edk2/code/trunk/edk2
>>>>>
>>>>>  Tianocore Stewards
>>>>> @@ -203,7 +202,7 @@ W:
>> https://github.com/tianocore/tianocore.github.io/wiki/OptionRomPkg
>>>>>  M: Ruiyu Ni <ruiyu.ni@intel.com>
>>>>>
>>>>>  OvmfPkg
>>>>> -W: http://www.tianocore.org/ovmf/
>>>>> +W: https://github.com/tianocore/tianocore.github.io/wiki/OVMF
>>>>>  M: Jordan Justen <jordan.l.justen@intel.com>
>>>>>  M: Laszlo Ersek <lersek@redhat.com>
>>>>>  M: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>>>>>
>>>>
>>>> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
>>>>
>>>> I can help push this change, but first let's wait for more feedback. I
>>>> think the only point that might see a bit of discussion is dropping
>>>> <git.code.sf.net> (as you highlight in your followup).
>>>>
>>>> Thanks!
>>>> Laszlo
>>
>>
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org
>> https://lists.01.org/mailman/listinfo/edk2-devel
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
> 



  reply	other threads:[~2019-02-26 12:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-23  5:18 [PATCH] Fix links in Maintainers.txt and remove slow, outdated sourceforge git mirror Rebecca Cran
2019-02-23  5:21 ` Rebecca Cran
2019-02-25 10:06 ` Laszlo Ersek
2019-02-25 13:36   ` Gao, Liming
2019-02-25 19:36     ` Laszlo Ersek
2019-02-25 23:56       ` Gao, Liming
2019-02-26 12:28         ` Laszlo Ersek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-03-24  2:00 [PATCH] Fix links in Maintainers.txt and remove slow " Rebecca Cran
2019-03-25 11:49 ` Laszlo Ersek
2019-03-25 12:28   ` Gao, Liming
2019-03-25 13:30   ` Rebecca Cran
2019-03-25 14:26     ` Laszlo Ersek

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=6800a51b-fa21-f325-bbc1-d17e3c8b62e2@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