public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Michael Kinney <michael.d.kinney@intel.com>
To: edk2-devel@lists.01.org
Cc: Laszlo Ersek <lersek@redhat.com>,
	Jordan Justen <jordan.l.justen@intel.com>,
	Liming Gao <liming.gao@intel.com>,
	Kevin W Shaw <kevin.w.shaw@intel.com>
Subject: [edk2-CCodingStandardsSpecification PATCH V2] Clarify format of multi-line function calls
Date: Mon, 12 Jun 2017 14:39:12 -0700	[thread overview]
Message-ID: <1497303553-19160-1-git-send-email-michael.d.kinney@intel.com> (raw)

https://bugzilla.tianocore.org/show_bug.cgi?id=425

GitHub branch for review:

* https://github.com/mdkinney/edk2-CCodingStandardsSpecification/tree/Bugzilla_425_ClarifyMultiLineFunctionCallFormat_V2

GitHub word diff view of the patches in this series:

* [1/1] https://github.com/mdkinney/edk2-CCodingStandardsSpecification/commit/880dd46e2068a06c87df128aa4955735ec7a07dc?w=1

Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Liming Gao <liming.gao@intel.com>
Cc: Kevin W Shaw <kevin.w.shaw@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Michael Kinney <michael.d.kinney@intel.com>

Michael Kinney (1):
  Clarify format of multi-line function calls

 5_source_files/52_spacing.md | 34 ++++++++++++++++------
 README.md                    | 69 ++++++++++++++++++++++----------------------
 2 files changed, 60 insertions(+), 43 deletions(-)

-- 
2.6.3.windows.1



             reply	other threads:[~2017-06-12 21:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12 21:39 Michael Kinney [this message]
2017-06-12 21:39 ` [edk2-CCodingStandardsSpecification PATCH V2] Clarify format of multi-line function calls Michael Kinney
2017-06-12 21:50   ` 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=1497303553-19160-1-git-send-email-michael.d.kinney@intel.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