public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>,
	Zenith432 <zenith432@users.sourceforge.net>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [PATCH] MdePkg: correct and clarify documentation of VA_LIST in Base.h
Date: Tue, 12 Dec 2017 18:42:23 +0100	[thread overview]
Message-ID: <185505b7-a1e3-71f2-81c2-d06663031e7e@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E191187@SHSMSX104.ccr.corp.intel.com>

On 12/12/17 16:01, Gao, Liming wrote:
> Laszlo:
>   Thanks!
> 
> Reviewed-by: Liming Gao <liming.gao@intel.com>

Thanks! Pushed it as e3e40c83fd2c.

Zenith432, thanks for the contribution -- for your next patch; please
send the updated versions as separate top-level postings, such as [PATCH
v2], [PATCH v3] etc. It seems that your original posting in this thread
was sent just fine with git-send-email, but the updated variants were
just pasted into emails using Thunderbird. So, in order to apply the
final version, I had to reconstruct the commit manually from the email.
That's a bit error prone (and slow).

"git format-patch" takes an option of the form "-v2", "-v3" etc; it will
fill in the subject prefix accordingly.

If you want to add extra comments on the patch just about the v1->v2,
v2->v3 differences, there are two possibilities:

- Simply add those remarks to the commit message. (Some edk2 developers
do this all the time, and it is fine IMO, although not the universally
recommended practice.)

- Use "git notes edit" to edit notes on commits -- they don't become
part of the commit message, and don't change the SHA1 commit hashes.
Then, use "git format-patch -v2 --notes" to format the updated version,
for mailing out. This will include the notes in a separate email
"section" such that humans will read it, but "git-am" / "git-push" will
not carry it over.

You can find more tips if you are interested, in:

https://github.com/tianocore/tianocore.github.io/wiki/Laszlo's-unkempt-git-guide-for-edk2-contributors-and-maintainers

Thanks!
Laszlo


      reply	other threads:[~2017-12-12 17:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1667068483.2112668.1512898346914.ref@mail.yahoo.com>
2017-12-10  9:32 ` [PATCH] MdePkg: correct and clarify documentation of VA_LIST in Base.h Zenith432
2017-12-10 13:53   ` Gao, Liming
2017-12-10 15:43     ` Zenith432
2017-12-11 14:35       ` Gao, Liming
2017-12-11 14:57         ` Zenith432
2017-12-12  1:32           ` Gao, Liming
2017-12-12  8:36             ` Laszlo Ersek
2017-12-12  9:16   ` Laszlo Ersek
2017-12-12 10:24     ` Zenith432
2017-12-12 10:39       ` Laszlo Ersek
2017-12-12 15:01         ` Gao, Liming
2017-12-12 17:42           ` Laszlo Ersek [this message]

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=185505b7-a1e3-71f2-81c2-d06663031e7e@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