public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <leif.lindholm@linaro.org>
To: Hao A Wu <hao.a.wu@intel.com>
Cc: devel@edk2.groups.io, rfc@edk2.groups.io,
	Liming Gao <liming.gao@intel.com>, Andrew Fish <afish@apple.com>,
	Laszlo Ersek <lersek@redhat.com>,
	Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [RFC][PATCH 0/1] Drop the SourceForge SVN mirror
Date: Thu, 27 Jun 2019 10:08:07 +0100	[thread overview]
Message-ID: <20190627090807.t5mzgg7kjt2zdscp@bivouac.eciton.net> (raw)
In-Reply-To: <20190627055044.5476-1-hao.a.wu@intel.com>

On Thu, Jun 27, 2019 at 01:50:43PM +0800, Hao A Wu wrote:
> The patch proposes to:
> 
> A. Remove the information on the SourceForge SVN mirror repository from
>    the Maintainers.txt file.
> B. Stop the sync of the SourceForge SVN mirror from the upstream Github
>    Git repository. (At this moment, the SVN mirror is still syncing the
>    latest changes)
> 
> Cc: Liming Gao <liming.gao@intel.com>
> Cc: Andrew Fish <afish@apple.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Cc: Leif Lindholm <leif.lindholm@linaro.org>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>

>From my point of view, a strong:
Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>

But please wait for additional feedback before pushing.

> Hao A Wu (1):
>   Maintainers.txt: Drop deprecated SourceForge SVN link
> 
>  Maintainers.txt | 1 -
>  1 file changed, 1 deletion(-)
> 
> -- 
> 2.12.0.windows.1
> 

      parent reply	other threads:[~2019-06-27  9:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27  5:50 [RFC][PATCH 0/1] Drop the SourceForge SVN mirror Wu, Hao A
2019-06-27  5:50 ` [RFC][PATCH 1/1] Maintainers.txt: Drop deprecated SourceForge SVN link Wu, Hao A
2019-06-27 11:59   ` Laszlo Ersek
2019-07-03  7:20     ` [edk2-devel] " Wu, Hao A
2019-07-04  0:10       ` Wu, Hao A
2019-06-27  9:08 ` Leif Lindholm [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=20190627090807.t5mzgg7kjt2zdscp@bivouac.eciton.net \
    --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