public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Patrick Georgi <pgeorgi@google.com>
To: "Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>
Cc: edk2-devel@lists.01.org
Subject: Re: [PATCH 3/3] IntelFsp2Pkg: Tell git to format SplitFspBin.py with native newlines
Date: Tue, 18 Sep 2018 17:53:26 +0200	[thread overview]
Message-ID: <CAE-gjdW89wvX5=EVrMfq7=EwPZUtehjy4fMSuqoiDeHEUXjo-w@mail.gmail.com> (raw)
In-Reply-To: <5608C728-C8C9-4D20-8C4D-FEC4FA974BA6@intel.com>

Am Di., 18. Sep. 2018 um 17:10 Uhr schrieb Desimone, Nathaniel L <
nathaniel.l.desimone@intel.com>:

> The EDK2 coding standard specifies that all files should be in CR-LF
> format. Please see the following:
> https://edk2-docs.gitbooks.io/edk-ii-c-coding-standards-specification/content/5_source_files/#51-general-rules

Thank you for the pointer!

Is the .gitattributes file alone sufficient?
>
The conversion of the file is for the repo-internal representation (which
defaults to LF given git's origin on unix-like systems). According to the
docs, due to the "text" property it should still checkout with CRLF on CRLF
platforms (as long as core.eol is kept at its default "native" value,
otherwise core.eol and core.autocrlf will influence that decision). I don't
have such a system around, so my ability to test is limited.

The problem with having CRLF in the file on unixoids is that it elicits an
error like the following when calling it directly:
$ IntelFsp2Pkg/Tools/SplitFspBin.py
/usr/bin/env: 'python\r': No such file or directory

If the autoconversion is not considered good enough, I'd propose keeping
out patch 1 of this series that adds the #! line and the executable bit,
and instead expect people to always call the script with "python
$path/SplitFspBin.py" to keep confusion at a minimum.


Regards,
Patrick


  reply	other threads:[~2018-09-18 15:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-18 13:32 [PATCH 1/3] IntelFsp2Pkg: Allow calling SplitFspBin.py directly Patrick Georgi
2018-09-18 13:32 ` [PATCH 2/3] IntelFsp2Pkg: Fix typo in SplitFspBin Patrick Georgi
2018-09-18 15:04   ` Desimone, Nathaniel L
2018-09-20 23:28     ` Chiu, Chasel
2018-09-26  3:11       ` Yao, Jiewen
2018-09-18 13:32 ` [PATCH 3/3] IntelFsp2Pkg: Tell git to format SplitFspBin.py with native newlines Patrick Georgi
2018-09-18 15:10   ` Desimone, Nathaniel L
2018-09-18 15:53     ` Patrick Georgi [this message]
2018-09-20  4:37       ` Desimone, Nathaniel L
2018-09-26  3:12         ` Yao, Jiewen
2018-09-26 15:58           ` Patrick Georgi
2018-09-27  0:40             ` Yao, Jiewen
2018-09-18 15:03 ` [PATCH 1/3] IntelFsp2Pkg: Allow calling SplitFspBin.py directly Desimone, Nathaniel L

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='CAE-gjdW89wvX5=EVrMfq7=EwPZUtehjy4fMSuqoiDeHEUXjo-w@mail.gmail.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