public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [Patch] edk2 Readme.md: Add edk2 release tag and edk2 release plan
Date: Wed, 12 Dec 2018 13:52:15 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E38B98A@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <0b2bd66d-95bc-9695-8c10-e73a7f8fe5da@redhat.com>

Laszlo:
  Sorry for the confuse. I don't find the good name for them. I think your suggestion is good. I will keep it. 

Thanks
Liming
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Laszlo Ersek
> Sent: Wednesday, December 12, 2018 6:22 PM
> To: Gao, Liming <liming.gao@intel.com>; edk2-devel@lists.01.org
> Subject: Re: [edk2] [Patch] edk2 Readme.md: Add edk2 release tag and edk2 release plan
> 
> Hi Liming,
> 
> On 12/12/18 01:41, Gao, Liming wrote:
> > Hi, all
> >   I don't get any comments on this change. So, I will push it this week.
> 
> sorry that I didn't respond earlier.
> 
> I think the structure of your patch series is confusing. The first patch
> is for the edk2 project README file. I saw that soon after you posted
> these patches, and I thought someone else should comment on the series.
> So I skipped the rest of the series as well.
> 
> However, the second patch in the series (which is not numbered, but I
> can see the second patch was sent threaded under the first), is for the
> edk2 *wiki*. I think that's extremely confusing, modifying multiple
> *repositories* in a single patch email thread. The wiki patch should
> have been sent separately.
> 
> Furthermore, the subject shouldn't be
> 
>   [edk2] [Patch] edk2 wiki: remove ...
> 
> but
> 
>   [edk2] [Patch edk2-wiki] remove ...
> 
> For two reasons:
> 
> - This way reviewers will see at once that the *project* (repo) in
> question is the wiki. We always put the repo (e.g. edk2-platforms,
> edk2-staging) in the bracketed part.
> 
> - When the patch is finally pushed to the wiki, the subject line of the
> commit should not say "edk2 wiki". The commit is made to the wiki repo
> anyway, so naming it in the commit message is redundant.
> 
> 
> Anyway, beyond the above meta-comments, I'm fine with the contents of
> the patches themselves. The article at
> <https://github.com/tianocore/edk2/releases/tag/edk2-stable201811>
> preserves the list of features added in the November release. That link
> is added to Readme.md in the first patch, and in general,
> <https://github.com/tianocore/edk2/releases> is a generic feature of
> github, for all projects.
> 
> Thanks,
> Laszlo
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


      reply	other threads:[~2018-12-12 13:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05 14:49 [Patch] edk2 Readme.md: Add edk2 release tag and edk2 release plan Liming Gao
2018-12-05 14:49 ` [Patch] edk2 wiki: remove edk2-stable201811 tag planning in EDK-II-Release-Planning Liming Gao
2018-12-12  0:41 ` [Patch] edk2 Readme.md: Add edk2 release tag and edk2 release plan Gao, Liming
2018-12-12 10:22   ` Laszlo Ersek
2018-12-12 13:52     ` Gao, Liming [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=4A89E2EF3DFEDB4C8BFDE51014F606A14E38B98A@SHSMSX104.ccr.corp.intel.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