From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Sami Mujawar <sami.mujawar@arm.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
edk2-devel-groups-io <devel@edk2.groups.io>,
"nd@arm.com" <nd@arm.com>,
Leif Lindholm <quic_llindhol@quicinc.com>
Subject: Re: Incorrect push to edk2-platforms
Date: Fri, 29 Jul 2022 13:27:29 -0700 [thread overview]
Message-ID: <CAMj1kXG=35s+LLQO3+osc3gyW0bXY9YU7O5-qxmZXtKXEFcEJQ@mail.gmail.com> (raw)
In-Reply-To: <CO1PR11MB49297057D31B91FCAE6409C4D2999@CO1PR11MB4929.namprd11.prod.outlook.com>
Reverting and reapplying kind of defeats the purpose, to be honest.
The merge commit is still part of the history, and so its effect
during a bisect will be there regardless.
So I suggest we just leave this as is.
On Fri, 29 Jul 2022 at 13:20, Kinney, Michael D
<michael.d.kinney@intel.com> wrote:
>
> Hi Sami,
>
> There is one other instance of this in edk2-platform history.
>
> It was immediately followed by a Revert.
>
> --------------
> commit 3e31cfea3de2fe49b49a67a1d6c9f9ca09e7f332
> Author: Siyuan Fu <siyuan.fu@intel.com>
> Date: Mon Feb 10 12:29:48 2020 +0800
>
> Revert "Merge remote-tracking branch 'upstream/master'"
>
> This reverts commit afb07dacda55f4f378fabf2e55172a95d01e5df4, reversing
> changes made to 3f0d14bb1358dfadef65dbd22c8f6d3b89471d49.
>
> commit afb07dacda55f4f378fabf2e55172a95d01e5df4
> Merge: 0c86cf06ed 3f0d14bb13
> Author: Siyuan Fu <siyuan.fu@intel.com>
> Date: Mon Feb 10 11:49:14 2020 +0800
>
> Merge remote-tracking branch 'upstream/master'
> --------------
>
> Reverting the merge commit and adding the changes correctly
> may be the cleanest way to address.
>
> Best regards,
>
> Mike
>
> > -----Original Message-----
> > From: Sami Mujawar <sami.mujawar@arm.com>
> > Sent: Friday, July 29, 2022 1:14 PM
> > To: Ard Biesheuvel <ardb+tianocore@kernel.org>; edk2-devel-groups-io <devel@edk2.groups.io>; nd@arm.com; Leif Lindholm
> > <quic_llindhol@quicinc.com>; Kinney, Michael D <michael.d.kinney@intel.com>
> > Subject: Re: Incorrect push to edk2-platforms
> >
> > Adding Leif and Mike.
> >
> > On 29/07/2022 08:54 pm, Sami Mujawar wrote:
> > > Hi Ard,
> > >
> > > I have accidentally pushed a change to the edk2-platforms repo.
> > >
> > > The commit is
> > >
> > > 2faefb2bbcc8083e1bd28908c0b29b5d18595298 <Sami Mujawar> Merge branch
> > > 'master' of github.com:/tianocore/edk2-platforms
> > >
> > > Appologies for the trouble. Can you advise on how this can be fixed,
> > > please?
> > >
> > > Regards,
> > >
> > > Sami Mujawar
> > >
> > >
> > >
> > 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.
next prev parent reply other threads:[~2022-07-29 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 19:54 Incorrect push to edk2-platforms Sami Mujawar
2022-07-29 20:13 ` Sami Mujawar
2022-07-29 20:18 ` Ard Biesheuvel
2022-07-29 20:20 ` Michael D Kinney
2022-07-29 20:27 ` Ard Biesheuvel [this message]
2022-07-29 20:40 ` [edk2-devel] " Michael D Kinney
2022-07-29 21:11 ` Sami Mujawar
2022-07-29 21:01 ` Sami Mujawar
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='CAMj1kXG=35s+LLQO3+osc3gyW0bXY9YU7O5-qxmZXtKXEFcEJQ@mail.gmail.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