From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <jbrasen@nvidia.com>
Cc: <bob.c.feng@intel.com>, <yuwei.chen@intel.com>
Subject: 回复: [edk2-devel] [PATCH] .gitignore: Ignore build tools build logs
Date: Wed, 18 May 2022 14:40:17 +0800 [thread overview]
Message-ID: <02ac01d86a82$2319dd60$694d9820$@byosoft.com.cn> (raw)
In-Reply-To: <1024c08deba6339ad9b41ffa89b23accf01eb33c.1650560339.git.jbrasen@nvidia.com>
Bob:
Do you know what files will be generated in BaseTools/BaseToolsBuild
directory?
Thanks
Liming
> -----邮件原件-----
> 发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Jeff Brasen
> via groups.io
> 发送时间: 2022年4月22日 1:01
> 收件人: devel@edk2.groups.io
> 抄送: bob.c.feng@intel.com; gaoliming@byosoft.com.cn;
> yuwei.chen@intel.com; Jeff Brasen <jbrasen@nvidia.com>
> 主题: [edk2-devel] [PATCH] .gitignore: Ignore build tools build logs
>
> The python BaseTools/Edk2ToolsBuild.py creates files in
> BaseTools/BaseToolsBuild and should be ignored.
>
> Signed-off-by: Jeff Brasen <jbrasen@nvidia.com>
> ---
> BaseTools/.gitignore | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/BaseTools/.gitignore b/BaseTools/.gitignore
> index a45689bc89..ddf93b7116 100644
> --- a/BaseTools/.gitignore
> +++ b/BaseTools/.gitignore
> @@ -17,4 +17,5 @@ Source/C/VfrCompile/VfrTokens.h
> Source/C/bin/
> Source/C/libs/
> Bin/Win32
> -Lib
> \ No newline at end of file
> +Lib
> +BaseToolsBuild/
> \ No newline at end of file
> --
> 2.25.1
>
>
>
>
>
next prev parent reply other threads:[~2022-05-18 6:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 17:01 [PATCH] .gitignore: Ignore build tools build logs Jeff Brasen
2022-05-18 2:58 ` [edk2-devel] " Jeff Brasen
2022-05-18 6:40 ` gaoliming [this message]
2022-05-18 7:14 ` Bob Feng
2022-05-20 1:19 ` 回复: " gaoliming
2022-06-17 15:38 ` Jeff Brasen
2022-07-07 18:14 ` Jeff Brasen
2022-07-09 13:46 ` Bob Feng
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='02ac01d86a82$2319dd60$694d9820$@byosoft.com.cn' \
--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