public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <leif.lindholm@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: devel@edk2.groups.io, Pete Batard <pete@akeo.ie>,
	ard.biesheuvel@linaro.org, samer.el-haj-mahmoud@arm.com,
	Laszlo Ersek <lersek@redhat.com>
Subject: Re: [edk2-devel] [edk2-platforms][PATCH v2 1/7] Platform/RPi: Add missing model name
Date: Tue, 19 Nov 2019 12:50:36 +0000	[thread overview]
Message-ID: <20191119125036.GC7323@bivouac.eciton.net> (raw)
In-Reply-To: <ae8c6650-907d-90f8-da33-943383f04359@redhat.com>

On Tue, Nov 19, 2019 at 01:25:51PM +0100, Philippe Mathieu-Daudé wrote:
> > > I feel really lost with how the S-o-b are handled.
> > 
> > Signed-off-by, as per https://developercertificate.org/, starts off
> > with "By making a contribution to this project, I certify that:".
> > 
> > That is only a valid statement at the point of contributing code to a
> > project. It is also only a valid statement when given by the person
> > contributing it. Samer has authored this code, but he has not
> > contributed it.
> > 
> > My own litmus test is the legal usefulness of the statament
> > "Samer said he signed the contract.".
> 
> I just asked clarification on another thread and now see this reply.
> 
> Now I understand that while being the author, Samer did not contributed his
> code to the project. Then by forwarding his work, Pete is a contributor
> signing the certificate. If Samer did not sign the certificate in front of
> the project (by posting his work), then Pete can not sign on his behalf.

Correct.

> Thanks for the clear explanation!

NP. I only wish I'd have seen this mail sooner :|

/
    Leif

  reply	other threads:[~2019-11-19 12:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 11:38 [edk2-platforms][PATCH v2 0/7] Platform/RPi: Early Raspberry Pi 4 groundwork Pete Batard
2019-11-19 11:38 ` [edk2-platforms][PATCH v2 1/7] Platform/RPi: Add missing model name Pete Batard
2019-11-19 12:02   ` Philippe Mathieu-Daudé
2019-11-19 12:14     ` [edk2-devel] " Leif Lindholm
2019-11-19 12:25       ` Philippe Mathieu-Daudé
2019-11-19 12:50         ` Leif Lindholm [this message]
2019-11-19 12:25     ` Pete Batard
2019-11-19 11:38 ` [edk2-platforms][PATCH v2 2/7] Platform/RPi: Add model family detection Pete Batard
2019-11-19 11:38 ` [edk2-platforms][PATCH v2 3/7] Platform/RPi: Replace Bcm283x SoC base register address with a PCD Pete Batard
2019-11-19 11:43   ` Philippe Mathieu-Daudé
2019-11-19 11:57     ` Pete Batard
2019-11-19 12:16       ` Philippe Mathieu-Daudé
2019-11-19 12:44         ` Leif Lindholm
2019-11-19 12:51           ` Ard Biesheuvel
2019-11-19 11:38 ` [edk2-platforms][PATCH v2 4/7] Platform/RPi: Use offsets for Bcm238x SoC register addresses Pete Batard
2019-11-19 11:46   ` Philippe Mathieu-Daudé
2019-11-19 11:38 ` [edk2-platforms][PATCH v2 5/7] Silicon/Broadcom: Add Bcm2711 header Pete Batard
2019-11-19 11:51   ` Philippe Mathieu-Daudé
2019-11-19 11:38 ` [edk2-platforms][PATCH v2 6/7] Platform/RPi: Read more variables from VideoCore during early init Pete Batard
2019-11-19 11:38 ` [edk2-platforms][PATCH v2 7/7] Platform/RPi: Clean up and improve early memory init Pete Batard
2019-11-19 18:20 ` [edk2-platforms][PATCH v2 0/7] Platform/RPi: Early Raspberry Pi 4 groundwork 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=20191119125036.GC7323@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