From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [Patch] BaseTools gitignore: Ignore VS intermediate files *.obj and *.pdb
Date: Tue, 15 Nov 2016 07:16:15 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F564844BFF@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <1479191390-30812-1-git-send-email-liming.gao@intel.com>
Liming,
When I do a build of BaseTools, I see some additional files in Pccts
with different extensions.
Mike
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Liming Gao
> Sent: Monday, November 14, 2016 10:30 PM
> To: edk2-devel@lists.01.org
> Subject: [edk2] [Patch] BaseTools gitignore: Ignore VS intermediate files *.obj
> and *.pdb
>
> Cc: Yonghong Zhu <yonghong.zhu@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Liming Gao <liming.gao@intel.com>
> ---
> BaseTools/.gitignore | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/BaseTools/.gitignore b/BaseTools/.gitignore
> index 5ca024c..d737258 100644
> --- a/BaseTools/.gitignore
> +++ b/BaseTools/.gitignore
> @@ -1,5 +1,7 @@
> *.d
> *.o
> +*.obj
> +*.pdb
> *.pyc
> Source/C/VfrCompile/EfiVfrParser.cpp
> Source/C/VfrCompile/EfiVfrParser.h
> --
> 2.8.0.windows.1
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2016-11-15 7:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 6:29 [Patch] BaseTools gitignore: Ignore VS intermediate files *.obj and *.pdb Liming Gao
2016-11-15 7:03 ` Zhu, Yonghong
2016-11-15 7:16 ` Kinney, Michael D [this message]
2016-11-15 10:39 ` [PATCH v2] " Liming Gao
2016-11-15 16:25 ` Kinney, Michael D
2016-11-16 1:27 ` Gao, Liming
2016-11-16 16:36 ` Kinney, Michael D
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=E92EE9817A31E24EB0585FDF735412F564844BFF@ORSMSX113.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