public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Leif Lindholm <leif.lindholm@linaro.org>,
	Jordan Justen <jordan.l.justen@intel.com>
Cc: edk2-devel@ml01.01.org, Ruiyu Ni <ruiyu.ni@intel.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Andrew Fish <afish@apple.com>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	David Wei <david.wei@intel.com>
Subject: Re: [PATCH 0/7] Various: Remove EDK2 use of IntelFrameworkModulePkg legacy libs
Date: Fri, 2 Dec 2016 12:53:45 +0100	[thread overview]
Message-ID: <f0ec840f-61f5-dc56-011c-e7f3683bd23b@redhat.com> (raw)
In-Reply-To: <20161202112708.GT27069@bivouac.eciton.net>

On 12/02/16 12:27, Leif Lindholm wrote:
> On Thu, Dec 01, 2016 at 11:38:42AM -0800, Jordan Justen wrote:
>> For the future, I'd recommend adding Cc's for package owners to the
>> associated patch commit message.
> 
> I guess what you're actually asking for is to have only the parts of
> series I want your review on sent to you?
> 
> That's a fair point, but having Cc: tags of package maintainers in the
> commit log is just noise.

Strongly disagree, I fully *want* the commit log to capture the fact
that I CC'd X, Y and Z, and if the committed patch doesn't have feedback
tags from them, that's not my fault.

Independently, technically speaking, there's also no other way for
assigning different sets of CC's to different patches in a series, to my
knowledge. There are hacks around it (for example, you can mail out each
patch individually, setting the CC's per mailing, or else edit the CC
headers (not commit message tags) in the formatted patch email), but
none of those stick around when you rebase the work for v2 or v3, and
format and send out the series again.

> And we are indeed seeing a lot of those at
> the moment.
> 
> This seems like an excellent time to bring back the idea of unifying
> the */Contributions.txt and codifying some of this behaviour
> better. (None of them mention Cc: - and they are in fact all
> bit-identical.)

Well, my personal guide mentions Cc:

https://github.com/tianocore/tianocore.github.io/wiki/Laszlo's-unkempt-git-guide-for-edk2-contributors-and-maintainers#contrib-18

Thanks
Laszlo

> Rather than derailing this thread, how about I send out a patch that
> does just that, and then we can discuss modifications to the document?
> 
>> Series Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
> 
> Many thanks - I'll apply for your packages.
> 
> Regards,
> 
> Leif
> 
>> On 2016-12-01 07:53:19, Leif Lindholm wrote:
>>> LzmaCustomDecompressLib and PeiDxeDebugLibReportStatusCode were copied
>>> from IntelFrameworkModulePkg to MdeModulePkg, but the originals were
>>> kept for compatibility.
>>>
>>> Nevertheless, new code should be using the MdeModulePkg versions, so
>>> change all references in in-tree platforms.
>>>
>>> Since the patches are individually independent, I plan to push them
>>> myself as Reviewed-by:s appear. Laszlo/Mike - Are you OK with me pusing
>>> 1 and 2 myself before the whole series is reviewed?
>>>
>>> Changes from RFC:
>>> - Broken down into per-package patches.
>>> - Received Reviewed-by:s added.
>>>
>>> Leif Lindholm (7):
>>>   OvmfPkg: Remove use of IntelFrameworkModulePkg legacy libs
>>>   QuarkSocPkg: Remove use of IntelFrameworkModulePkg legacy libs
>>>   BeagleBoardPkg: Remove use of IntelFrameworkModulePkg legacy libs
>>>   EmbeddedPkg: Remove use of IntelFrameworkModulePkg legacy libs
>>>   DuetPkg: Remove use of IntelFrameworkModulePkg legacy libs
>>>   EmulatorPkg: Remove use of IntelFrameworkModulePkg legacy libs
>>>   Vlv2TbltDevicePkg: Remove use of IntelFrameworkModulePkg legacy libs
>>>
>>>  BeagleBoardPkg/BeagleBoardPkg.dsc       | 4 ++--
>>>  DuetPkg/DuetPkgIa32.dsc                 | 4 ++--
>>>  DuetPkg/DuetPkgX64.dsc                  | 4 ++--
>>>  EmbeddedPkg/EmbeddedPkg.dsc             | 2 +-
>>>  EmulatorPkg/EmulatorPkg.dsc             | 4 ++--
>>>  OvmfPkg/OvmfPkgIa32.dsc                 | 4 ++--
>>>  OvmfPkg/OvmfPkgIa32X64.dsc              | 4 ++--
>>>  OvmfPkg/OvmfPkgX64.dsc                  | 4 ++--
>>>  QuarkSocPkg/QuarkSocPkg.dsc             | 2 +-
>>>  Vlv2TbltDevicePkg/PlatformPkgGccX64.dsc | 4 ++--
>>>  Vlv2TbltDevicePkg/PlatformPkgIA32.dsc   | 6 +++---
>>>  Vlv2TbltDevicePkg/PlatformPkgX64.dsc    | 6 +++---
>>>  12 files changed, 24 insertions(+), 24 deletions(-)
>>>
>>> -- 
>>> 2.10.2
>>>
>>> _______________________________________________
>>> edk2-devel mailing list
>>> edk2-devel@lists.01.org
>>> https://lists.01.org/mailman/listinfo/edk2-devel



  reply	other threads:[~2016-12-02 11:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-01 15:53 [PATCH 0/7] Various: Remove EDK2 use of IntelFrameworkModulePkg legacy libs Leif Lindholm
2016-12-01 15:53 ` [PATCH 1/7] OvmfPkg: Remove " Leif Lindholm
2016-12-01 18:24   ` Laszlo Ersek
2016-12-01 15:53 ` [PATCH 2/7] QuarkSocPkg: " Leif Lindholm
2016-12-01 15:53 ` [PATCH 3/7] BeagleBoardPkg: " Leif Lindholm
2016-12-01 15:53 ` [PATCH 4/7] EmbeddedPkg: " Leif Lindholm
2016-12-01 15:53 ` [PATCH 5/7] DuetPkg: " Leif Lindholm
2016-12-02  2:01   ` Ni, Ruiyu
2016-12-01 15:53 ` [PATCH 6/7] EmulatorPkg: " Leif Lindholm
2016-12-01 15:53 ` [PATCH 7/7] Vlv2TbltDevicePkg: " Leif Lindholm
2016-12-05 17:32   ` Leif Lindholm
2016-12-06  6:28     ` Wei, David
2016-12-06  9:22       ` Leif Lindholm
2016-12-01 18:14 ` [PATCH 0/7] Various: Remove EDK2 " Kinney, Michael D
2016-12-01 19:38 ` Jordan Justen
2016-12-02 11:27   ` Leif Lindholm
2016-12-02 11:53     ` Laszlo Ersek [this message]
2016-12-02 12:02       ` Leif Lindholm
2016-12-02 16:13 ` Leif Lindholm
2016-12-05 15:38   ` Ard Biesheuvel
2016-12-05 16:02     ` Leif Lindholm

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=f0ec840f-61f5-dc56-011c-e7f3683bd23b@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