public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Jordan Justen <jordan.l.justen@intel.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Leif Lindholm <leif.lindholm@linaro.org>,
	Andrew Fish <afish@apple.com>,
	"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [Patch 1/2] BaseTools/PatchCheck: Support Contribution Agreement 1.1
Date: Tue, 18 Jul 2017 09:12:52 -0700	[thread overview]
Message-ID: <150039437240.2449.15892869732817184679@jljusten-skl> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5A7D5C967@ORSMSX113.amr.corp.intel.com>

On 2017-07-18 08:59:46, Kinney, Michael D wrote:
> Hi Jordan,
> 
> I can update the logic.  The loop of supported
> version values looks good.
> 
> One of the reasons I choose the style I did is that 
> this patch is intended to be short lived.  I would
> like to see everyone transition to the new agreement
> in their commit messages.  I know there are patches 
> in progress, so we need a period of time where both
> are supported.  I a month or two, I would like to 
> require the 1.1 agreement in the commit messages.
> 
> Adding flexibility in the compare did not make much
> sense if we are going to use one most of the time.

Oh. Good point. What about something like:

    def check_contributed_under(self):
        cu_msg='Contributed-under: TianoCore Contribution Agreement 1.1'
        if self.msg.find(cu_msg) < 0:
            # Allow 1.0 for now while EDK II community transitions to 1.1
            cu_msg='Contributed-under: TianoCore Contribution Agreement 1.0'
            if self.msg.find(cu_msg) < 0:
                self.error('Missing Contributed-under! (Note: this must be ' +
                           'added by the code contributor!)')

And, maybe we could mention in the commit message that allowing 1.0 is
temporary?

With that: Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>


  reply	other threads:[~2017-07-18 16:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17 21:28 [Patch 0/2] Update to Tiano Contribution Agreement 1.1 Michael D Kinney
2017-07-17 21:28 ` [Patch 1/2] BaseTools/PatchCheck: Support " Michael D Kinney
2017-07-17 22:13   ` Jordan Justen
2017-07-18 15:59     ` Kinney, Michael D
2017-07-18 16:12       ` Jordan Justen [this message]
2017-07-17 21:28 ` [Patch 2/2] edk2: Update to Tiano " Michael D Kinney
2017-07-18  0:01   ` Jordan Justen
2017-07-18 18:24     ` Kinney, Michael D
2017-07-17 21:43 ` [Patch 0/2] " 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=150039437240.2449.15892869732817184679@jljusten-skl \
    --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