public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
	edk2-devel-01 <edk2-devel@lists.01.org>
Cc: Thomas Huth <thuth@redhat.com>, "Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: [PATCH] BaseTools/BuildEnv: override "set -C" (noclobber) in sourcing shell env
Date: Wed, 18 Oct 2017 08:01:43 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E16D542@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20171017211234.13730-1-lersek@redhat.com>

Reviewed-by: Liming Gao <liming.gao@intel.com>

>-----Original Message-----
>From: Laszlo Ersek [mailto:lersek@redhat.com]
>Sent: Wednesday, October 18, 2017 5:13 AM
>To: edk2-devel-01 <edk2-devel@lists.01.org>
>Cc: Gao, Liming <liming.gao@intel.com>; Thomas Huth <thuth@redhat.com>;
>Zhu, Yonghong <yonghong.zhu@intel.com>
>Subject: [PATCH] BaseTools/BuildEnv: override "set -C" (noclobber) in
>sourcing shell env
>
>The BuildEnv utility is sourced (executed by the user's interactive shell)
>when the user sets up the build session. Some users like to set -C
>(noclobber) for some additional safety in their shells, which trips up
>BuildEnv. Update the redirection operator so that it overrides noclobber.
>
>Cc: Liming Gao <liming.gao@intel.com>
>Cc: Thomas Huth <thuth@redhat.com>
>Cc: Yonghong Zhu <yonghong.zhu@intel.com>
>Contributed-under: TianoCore Contribution Agreement 1.1
>Signed-off-by: Laszlo Ersek <lersek@redhat.com>
>---
>
>Notes:
>    Repo:   https://github.com/lersek/edk2.git
>    Branch: buildenv_clobber
>
> BaseTools/BuildEnv | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/BaseTools/BuildEnv b/BaseTools/BuildEnv
>index f74881111c8e..ff0c5115a5e1 100755
>--- a/BaseTools/BuildEnv
>+++ b/BaseTools/BuildEnv
>@@ -90,7 +90,7 @@ StoreCurrentConfiguration() {
>   #
>   OUTPUT_FILE=$CONF_PATH/BuildEnv.sh
>   #echo Storing current configuration into $OUTPUT_FILE
>-  echo "# Auto-generated by ${BASH_SOURCE[0]}" > $OUTPUT_FILE
>+  echo "# Auto-generated by ${BASH_SOURCE[0]}" >| $OUTPUT_FILE
>   GenerateShellCodeToSetVariable WORKSPACE $OUTPUT_FILE
>   GenerateShellCodeToSetVariable EDK_TOOLS_PATH $OUTPUT_FILE
>   GenerateShellCodeToUpdatePath $OUTPUT_FILE
>--
>2.14.1.3.gb7cf6e02401b



  reply	other threads:[~2017-10-18  7:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17 21:12 [PATCH] BaseTools/BuildEnv: override "set -C" (noclobber) in sourcing shell env Laszlo Ersek
2017-10-18  8:01 ` Gao, Liming [this message]
     [not found] ` <eb415ec8-bfbf-bd02-b5c1-7cb2c4c04c21@redhat.com>
2017-10-18  8:42   ` Laszlo Ersek
2017-10-18  9:37 ` Laszlo Ersek

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=4A89E2EF3DFEDB4C8BFDE51014F606A14E16D542@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