public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Evan Lloyd <Evan.Lloyd@arm.com>
To: Laszlo Ersek <lersek@redhat.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "\"ard.biesheuvel@linaro.org\"@arm.com"
	<"ard.biesheuvel@linaro.org"@arm.com>,
	"\"leif.lindholm@linaro.org\"@arm.com"
	<"leif.lindholm@linaro.org"@arm.com>,
	"\"Matteo.Carlini@arm.com\"@arm.com"
	<"Matteo.Carlini@arm.com"@arm.com>,
	"\"lersek@redhat.com\"@arm.com" <"lersek@redhat.com"@arm.com>,
	"\"liming.gao@intel.com\"@arm.com"
	<"liming.gao@intel.com"@arm.com>,
	"\"michael.d.kinney@intel.com\"@arm.com"
	<"michael.d.kinney@intel.com"@arm.com>,
	"\"jordan.l.justen@intel.com\"@arm.com"
	<"jordan.l.justen@intel.com"@arm.com>,
	"\"nd@arm.com\"@arm.com" <"nd@arm.com"@arm.com>
Subject: Re: [edk2-CCodingStandardsSpecification PATCH 4/5] Fix Chapter 4 Typo
Date: Thu, 4 Jan 2018 19:47:21 +0000	[thread overview]
Message-ID: <HE1PR08MB2684EB63D5550EF7DBFE70A48B1F0@HE1PR08MB2684.eurprd08.prod.outlook.com> (raw)



> -----Original Message-----
> From: Laszlo Ersek [mailto:lersek@redhat.com]
> Sent: 03 January 2018 16:56
> To: Evan Lloyd <Evan.Lloyd@arm.com>; edk2-devel@lists.01.org
> Cc: "ard.biesheuvel@linaro.org"@arm.com;
> "leif.lindholm@linaro.org"@arm.com;
> "Matteo.Carlini@arm.com"@arm.com; "lersek@redhat.com"@arm.com;
> "liming.gao@intel.com"@arm.com;
> "michael.d.kinney@intel.com"@arm.com;
> "jordan.l.justen@intel.com"@arm.com; "nd@arm.com"@arm.com
> Subject: Re: [edk2-CCodingStandardsSpecification PATCH 4/5] Fix Chapter 4
> Typo
>
> On 01/03/18 12:22, evan.lloyd@arm.com wrote:
> > From: Evan Lloyd <evan.lloyd@arm.com>
> >
> > 4.1.3.2 - remove "See" from 'as specified in See "File Heading"'
> >
> > Contributed-under: TianoCore Contribution Agreement 1.1
> > Signed-off-by: Evan Lloyd <evan.lloyd@arm.com>
> > ---
> >  4_naming_conventions/README.md | 418 ++++++++++----------
> >  1 file changed, 209 insertions(+), 209 deletions(-)
>
> Looks like this file underwent a line terminator conversion as well.
>
> If the file is currently not using CRLF, then I agree it should be converted;
> however, the conversion should be please separated from the typo fix.
>
> ... Hmm, the file already seems to use CRLF. So I think the conversion was to
> LF, and must have been unintended.

 [[Evan Lloyd]] It certainly was unintended, and seems to be an artefact of a core.autocrlf setting change.  Sorry.

>
> Can you please resubmit without the line terminator changes?
>
> Thanks!
> Laszlo
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:[~2018-01-04 19:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 19:47 Evan Lloyd [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-01-03 11:22 [edk2-CCodingStandardsSpecification PATCH 0/5] Typographic Corrections evan.lloyd
2018-01-03 11:22 ` [edk2-CCodingStandardsSpecification PATCH 4/5] Fix Chapter 4 Typo evan.lloyd
2018-01-03 16:56   ` Laszlo Ersek
2018-01-08 18:31     ` Evan Lloyd

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=HE1PR08MB2684EB63D5550EF7DBFE70A48B1F0@HE1PR08MB2684.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