public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Thomas Huth <thuth@redhat.com>, edk2-devel-01 <edk2-devel@lists.01.org>
Cc: Liming Gao <liming.gao@intel.com>, Yonghong Zhu <yonghong.zhu@intel.com>
Subject: Re: [PATCH] BaseTools/BuildEnv: override "set -C" (noclobber) in sourcing shell env
Date: Wed, 18 Oct 2017 10:42:07 +0200	[thread overview]
Message-ID: <7e75db0c-208f-f564-70c4-f10d3605454b@redhat.com> (raw)
In-Reply-To: <eb415ec8-bfbf-bd02-b5c1-7cb2c4c04c21@redhat.com>

Responding to this email because Thomas may not be subscribed to
edk2-devel, and edk2-devel *still* drops emails from non-subscribers
(which I think is extremely rude, see
<https://bugzilla.tianocore.org/show_bug.cgi?id=451>, but I'm really out
of devices to make the right thing happen):

On 10/18/17 10:00, Thomas Huth wrote:
> On 17.10.2017 23:12, Laszlo Ersek wrote:
>> 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
>>
> 
> FWIW:
> 
> Reviewed-by: Thomas Huth <thuth@redhat.com>
> 

So, now Thomas's R-b can be seen on the list as well.

Thank you!
Laszlo


  parent reply	other threads:[~2017-10-18  8:38 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
     [not found] ` <eb415ec8-bfbf-bd02-b5c1-7cb2c4c04c21@redhat.com>
2017-10-18  8:42   ` Laszlo Ersek [this message]
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=7e75db0c-208f-f564-70c4-f10d3605454b@redhat.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