public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Carsey, Jaben" <jaben.carsey@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Gao, Liming" <liming.gao@intel.com>,
	"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: [PATCH v3 1/1] BaseTools: Ecc - add dict for config file to internal translation
Date: Fri, 4 May 2018 21:47:49 +0000	[thread overview]
Message-ID: <CB6E33457884FA40993F35157061515CA3CEE4B2@FMSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <4070bbbd-a29f-8ea0-34e3-e8b9a2748498@redhat.com>

Thanks.  I don’t push BaseTools, but will await Liming or Yonghong to review and push.

Yonghong/Liming,  Can you strip the trailing space before you commit?

-Jaben

> -----Original Message-----
> From: Laszlo Ersek [mailto:lersek@redhat.com]
> Sent: Friday, May 04, 2018 2:44 PM
> To: Carsey, Jaben <jaben.carsey@intel.com>; edk2-devel@lists.01.org
> Cc: Gao, Liming <liming.gao@intel.com>; Zhu, Yonghong
> <yonghong.zhu@intel.com>
> Subject: Re: [PATCH v3 1/1] BaseTools: Ecc - add dict for config file to internal
> translation
> Importance: High
> 
> Hi Jaben.
> 
> On 05/04/18 22:25, Jaben Carsey wrote:
> > Commit eece4292acc80 changed a variable name, which was tied directly to
> > a config file entry. This seperates the internal variable names from
> > the config file entries by having the internal dict accessed through a
> > translation of key words.
> >
> > added a test when this is run straight from command line.
> >
> > Cc: Liming Gao <liming.gao@intel.com>
> > Cc: Yonghong Zhu <yonghong.zhu@intel.com>
> > Cc: Laszlo Ersek <lersek@redhat.com>
> > Contributed-under: TianoCore Contribution Agreement 1.1
> > Signed-off-by: Jaben Carsey <jaben.carsey@intel.com>
> > ---
> >  BaseTools/Source/Python/Ecc/Configuration.py | 122
> +++++++++++++++++++-
> >  1 file changed, 119 insertions(+), 3 deletions(-)
> >
> > diff --git a/BaseTools/Source/Python/Ecc/Configuration.py
> b/BaseTools/Source/Python/Ecc/Configuration.py
> > index b5b583be8c4a..d305182a2666 100644
> > --- a/BaseTools/Source/Python/Ecc/Configuration.py
> > +++ b/BaseTools/Source/Python/Ecc/Configuration.py
> > @@ -1,7 +1,7 @@
> >  ## @file
> >  # This file is used to define class Configuration
> >  #
> > -# Copyright (c) 2008 - 2017, Intel Corporation. All rights reserved.<BR>
> > +# Copyright (c) 2008 - 2018, Intel Corporation. All rights reserved.<BR>
> >  # This program and the accompanying materials
> >  # are licensed and made available under the terms and conditions of the
> BSD License
> >  # which accompanies this distribution.  The full text of the license may be
> found at
> > @@ -20,6 +20,109 @@ from Common.DataType import *
> >  from Common.String import *
> >  from Common.LongFilePathSupport import OpenLongFilePath as open
> >
> > +_ConfigFileToInternalTranslation = {
> > +    # not same
> > +    "ModifierList":"ModifierSet",
> > +
> 
> Git complains that the above line contains trailing whitespace.
> 
> But, that can be removed when you push this patch.
> 
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> 
> I've also run the Ecc tool (I didn't try to execute the self-test), and
> now it seems to work fine.
> 
> Tested-by: Laszlo Ersek <lersek@redhat.com>
> 
> Thanks!
> Laszlo

  reply	other threads:[~2018-05-04 21:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1525465447.git.jaben.carsey@intel.com>
2018-05-04 20:25 ` [PATCH v3 1/1] BaseTools: Ecc - add dict for config file to internal translation Jaben Carsey
2018-05-04 21:44   ` Laszlo Ersek
2018-05-04 21:47     ` Carsey, Jaben [this message]
2018-05-04 22:42       ` Laszlo Ersek
2018-05-05  1:21         ` Zhu, Yonghong

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=CB6E33457884FA40993F35157061515CA3CEE4B2@FMSMSX103.amr.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