public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Evan Lloyd <Evan.Lloyd@arm.com>
To: "edk2-devel (edk2-devel@lists.01.org)" <edk2-devel@lists.01.org>
Cc: "liming.gao@intel.com" <liming.gao@intel.com>,
	Leif Lindholm <leif.lindholm@linaro.org>
Subject: File mode problem on Github edk2-BaseTools-win32
Date: Fri, 11 Nov 2016 11:05:37 +0000	[thread overview]
Message-ID: <AM5PR0801MB17623DC1E7BAC5FE521B72E58BBB0@AM5PR0801MB1762.eurprd08.prod.outlook.com> (raw)

There is a minor, but annoying, problem with file modes on the Github edk2-BaseTools-win32 repository.
Git maintains a limited internal record of the Unix style file modes.
edk2-BaseTools-win32 currently causes Git to set the file's modes to 660.
So, after a checkout or pull of master, the builds fail because the files do not have Windows' "Read & Execute" permission.
This is simple to fix, but one has to remember (or, ofttimes, get reminded) to do it every time there is an update.

Liming,
Because this is purely a permission problem in the Git repository, and .exe files are not amenable to patching, I have raised a pull request on  https://github.com/tianocore/edk2-BaseTools-win32/pulls
This is only a minor thing, but I would deem it a great favour were you to accept the pull request.
It has me tearing my hair out, and I have little enough to begin with.  :-{

Regards,
Evan

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.


             reply	other threads:[~2016-11-11 11:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 11:05 Evan Lloyd [this message]
2016-11-11 11:24 ` File mode problem on Github edk2-BaseTools-win32 Laszlo Ersek
2016-11-11 13:12   ` Evan Lloyd
2016-11-11 13:57     ` 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=AM5PR0801MB17623DC1E7BAC5FE521B72E58BBB0@AM5PR0801MB1762.eurprd08.prod.outlook.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