public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"sean.brogan@microsoft.com" <sean.brogan@microsoft.com>,
	Bret Barkelew <Bret.Barkelew@microsoft.com>,
	"Gao, Liming" <liming.gao@intel.com>
Cc: "Leif Lindholm (Nuvia address)" <leif@nuviainc.com>,
	Andrew Fish <afish@apple.com>
Subject: Re: [edk2-devel] EDK II Maintainers - EDK II CI is now active on edk2/master
Date: Tue, 10 Mar 2020 08:53:27 +0100	[thread overview]
Message-ID: <5364bb7d-2a78-432d-deae-e648e24f4de4@redhat.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B9ECA053@ORSMSX113.amr.corp.intel.com>

On 03/09/20 22:44, Kinney, Michael D wrote:
> Laszlo,
> 
> If the dev branch that is being submitted as a PR
> contains the merge commit, or that developer use the
> one of the github features to rebase, the merge
> commit can be introduced.
> 
> When a PR is in this state, the developer need to
> clean up their history locally and do a forced
> push or open a new PR.
> 
> In the case, it looks like PatchCheck did a good
> job of rejecting a patch series we would not want
> added.

I agree that PatchCheck was right to refuse the merge commit, I'm just
very confused about the origin of that merge commit. The list of commits
noted in Ard's original PR did not include a merge commit. Also, it's
very unlikely for Ard to rely on github for a genuine rebase; he'd just
do it locally.

Anyway, the particular patches have now been merged correctly via
<https://github.com/tianocore/edk2/pull/431>.

Thanks!
Laszlo


  reply	other threads:[~2020-03-10  7:53 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-08 19:21 [edk2-devel] EDK II Maintainers - EDK II CI is now active on edk2/master Sean
2020-03-08 19:53 ` Michael D Kinney
2020-03-09 19:29   ` Laszlo Ersek
2020-03-09 19:32     ` Laszlo Ersek
2020-03-09 22:00       ` Michael D Kinney
2020-03-09 19:37     ` Laszlo Ersek
2020-03-09 20:06   ` Laszlo Ersek
2020-03-09 21:44     ` Michael D Kinney
2020-03-10  7:53       ` Laszlo Ersek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-12  2:55 Michael D Kinney
2019-11-12  8:56 ` [edk2-devel] " Laszlo Ersek
2019-11-12 19:50   ` Michael D Kinney
2019-11-12 19:52     ` Michael D Kinney
2019-11-13  7:56     ` Laszlo Ersek
2019-11-13  8:57 ` Laszlo Ersek
2019-11-13 16:23   ` Michael D Kinney
2019-11-13 17:03     ` Laszlo Ersek
2019-11-26  8:23 ` Laszlo Ersek
2019-11-27 19:03   ` Michael D Kinney
2019-11-28 12:00     ` Laszlo Ersek
2019-12-02 19:55       ` Michael D Kinney
2019-12-03  8:56         ` Laszlo Ersek
2019-12-03 17:07           ` Michael D Kinney
2019-12-03 20:39             ` Laszlo Ersek
2019-12-06 11:02 ` Laszlo Ersek
2019-12-06 11:07   ` Laszlo Ersek
2020-01-02 14:42 ` Philippe Mathieu-Daudé
2020-01-02 18:36   ` Michael D Kinney
2020-01-06 14:58     ` Philippe Mathieu-Daudé
2020-01-03 13:29   ` Laszlo Ersek
2020-01-06 17:29 ` Laszlo Ersek
2020-01-06 18:17   ` Michael D Kinney
2020-01-07  9:00     ` Laszlo Ersek
2020-01-09 21:30     ` Laszlo Ersek
2020-01-09 21:37       ` Michael D Kinney
2020-01-10 10:51         ` Laszlo Ersek
2020-03-08 11:12 ` 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=5364bb7d-2a78-432d-deae-e648e24f4de4@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