From: "Gao, Liming" <liming.gao@intel.com>
To: Leif Lindholm <leif.lindholm@linaro.org>,
"Feng, Bob C" <bob.c.feng@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [Patch V2] BaseTools: Fixed the build fail issue for cases
Date: Mon, 10 Dec 2018 14:36:59 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3898BC@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20181210123012.cswf2pbzppqxff27@bivouac.eciton.net>
Leif:
So, you don't think to need highlight which commit causes the regression issue in the commit message. I suggest to put this information into BZ description instead of commit message.
Thanks
Liming
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Leif Lindholm
> Sent: Monday, December 10, 2018 8:30 PM
> To: Feng, Bob C <bob.c.feng@intel.com>
> Cc: edk2-devel@lists.01.org; Gao, Liming <liming.gao@intel.com>
> Subject: Re: [edk2] [Patch V2] BaseTools: Fixed the build fail issue for cases
>
> Hi Bob,
>
> On Mon, Dec 10, 2018 at 09:16:58AM +0800, BobCF wrote:
> > From: "Feng, Bob C" <bob.c.feng@intel.com>
> >
> > V2:
>
> Patch version information does not belong in the commit message.
> It belongs in a cover letter, or if a cover letter is not used, you
> can put these details below the --- line. This way it gets filtered
> out by git.
>
> The patch commit message should end up being a description of what the
> patch is and does, not the development process that got us there.
>
> Regards,
>
> Leif
>
> > update the commit log. This issue is introduced by
> > the commit 72a1d77694d51914c0dd6aa97dbfa58634b0a4a5
> >
> > V1:
> > https://bugzilla.tianocore.org/show_bug.cgi?id=1386
> > 1. There is no Pcd value assignment in Dsc file
> > 2. There are duplicate Pcd filed assignment
> >
> > Contributed-under: TianoCore Contribution Agreement 1.1
> > Signed-off-by: Bob Feng <bob.c.feng@intel.com>
> > Cc: Liming Gao <liming.gao@intel.com>
> > ---
> > BaseTools/Source/Python/Workspace/BuildClassObject.py | 2 +-
> > BaseTools/Source/Python/Workspace/MetaFileParser.py | 2 +-
> > 2 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/BaseTools/Source/Python/Workspace/BuildClassObject.py b/BaseTools/Source/Python/Workspace/BuildClassObject.py
> > index 008eee1a16..d02232b546 100644
> > --- a/BaseTools/Source/Python/Workspace/BuildClassObject.py
> > +++ b/BaseTools/Source/Python/Workspace/BuildClassObject.py
> > @@ -289,11 +289,11 @@ class StructurePcd(PcdClassObject):
> > if DefaultStoreName not in self.SkuOverrideValues[SkuName]:
> > self.SkuOverrideValues[SkuName][DefaultStoreName] = OrderedDict()
> > if DimensionAttr not in self.SkuOverrideValues[SkuName][DefaultStoreName]:
> > self.SkuOverrideValues[SkuName][DefaultStoreName][DimensionAttr] = collections.OrderedDict()
> > if FieldName in self.SkuOverrideValues[SkuName][DefaultStoreName][DimensionAttr]:
> > - del self.SkuOverrideValues[SkuName][DefaultStoreName][FieldName][DimensionAttr]
> > + del self.SkuOverrideValues[SkuName][DefaultStoreName][DimensionAttr][FieldName]
> > self.SkuOverrideValues[SkuName][DefaultStoreName][DimensionAttr][FieldName] = [Value.strip(), FileName, LineNo]
> > return self.SkuOverrideValues[SkuName][DefaultStoreName][DimensionAttr][FieldName]
> >
> > def SetPcdMode (self, PcdMode):
> > self.PcdMode = PcdMode
> > diff --git a/BaseTools/Source/Python/Workspace/MetaFileParser.py b/BaseTools/Source/Python/Workspace/MetaFileParser.py
> > index 4bd52619a9..eaedba0c12 100644
> > --- a/BaseTools/Source/Python/Workspace/MetaFileParser.py
> > +++ b/BaseTools/Source/Python/Workspace/MetaFileParser.py
> > @@ -1201,11 +1201,11 @@ class DscParser(MetaFileParser):
> > else:
> > self._ValueList = None
> > return
> > TokenList = GetSplitValueList(self._CurrentLine, TAB_VALUE_SPLIT, 1)
> > self._CurrentPcdName = TokenList[0]
> > - if TokenList[1].strip().startswith("{CODE"):
> > + if len(TokenList) == 2 and TokenList[1].strip().startswith("{CODE"):
> > self._PcdDataTypeCODE = True
> > self._PcdCodeValue = TokenList[1].strip()
> >
> > if self._PcdDataTypeCODE:
> > if self._CurrentLine.endswith(")}"):
> > --
> > 2.19.1.windows.1
> >
> > _______________________________________________
> > edk2-devel mailing list
> > edk2-devel@lists.01.org
> > https://lists.01.org/mailman/listinfo/edk2-devel
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-12-10 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 1:16 [Patch V2] BaseTools: Fixed the build fail issue for cases BobCF
2018-12-10 12:30 ` Leif Lindholm
2018-12-10 14:36 ` Gao, Liming [this message]
2018-12-10 14:45 ` Leif Lindholm
2018-12-10 14:59 ` Gao, Liming
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=4A89E2EF3DFEDB4C8BFDE51014F606A14E3898BC@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