public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: 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 3/5] Fix Chapter 3 Typos
Date: Wed, 3 Jan 2018 17:53:22 +0100	[thread overview]
Message-ID: <2af37829-5fcd-fb5c-2eda-da175dcb5d64@redhat.com> (raw)
In-Reply-To: <20180103112248.11880-4-evan.lloyd@arm.com>

On 01/03/18 12:22, evan.lloyd@arm.com wrote:
> From: Evan Lloyd <evan.lloyd@arm.com>
> 
> 3_quick_reference.md has some obviously invalid extra characters at the
> end of line 55 ( ",).  This patch removes them.
> 
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Evan Lloyd <evan.lloyd@arm.com>
> ---
>  3_quick_reference.md | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/3_quick_reference.md b/3_quick_reference.md
> index 13045d297b3be848d91f9be05380454b4cc2fe91..9367e422fb0337007409d6597913cb43da92e0c5 100644
> --- a/3_quick_reference.md
> +++ b/3_quick_reference.md
> @@ -55,7 +55,7 @@
>    any file using the abbreviation or acronym. See "Abbreviation Usage" and
>    "Glossary".
>  
> -* There is no limit to name lengths. A length of 10 to 30 characters is ",
> +* There is no limit to name lengths. A length of 10 to 30 characters is
>    recommended. See "File Names" & "Identifiers that are always reserved".
>  
>  * File names must not start with numbers. See "File Names".
> 

Reviewed-by: Laszlo Ersek <lersek@redhat.com>



  reply	other threads:[~2018-01-03 16:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 11:22 [edk2-CCodingStandardsSpecification PATCH 0/5] Typographic Corrections evan.lloyd
2018-01-03 11:22 ` [edk2-CCodingStandardsSpecification PATCH 1/5] Fix Chapter 1 Typos evan.lloyd
2018-01-03 16:51   ` Laszlo Ersek
2018-01-04 19:40     ` Evan Lloyd
2018-01-03 11:22 ` [edk2-CCodingStandardsSpecification PATCH 2/5] Fix Chapter 2 Typos evan.lloyd
2018-01-03 16:52   ` Laszlo Ersek
2018-01-03 11:22 ` [edk2-CCodingStandardsSpecification PATCH 3/5] Fix Chapter 3 Typos evan.lloyd
2018-01-03 16:53   ` Laszlo Ersek [this message]
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
2018-01-03 11:22 ` [edk2-CCodingStandardsSpecification PATCH 5/5] Fix Chapter 5 Typos evan.lloyd
2018-01-03 17:07   ` Laszlo Ersek
2018-01-08 18:26     ` 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=2af37829-5fcd-fb5c-2eda-da175dcb5d64@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