public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney via groups.io" <michael.d.kinney=intel.com@groups.io>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"marcin.juszkiewicz@linaro.org" <marcin.juszkiewicz@linaro.org>
Cc: Leif Lindholm <quic_llindhol@quicinc.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [edk2-non-osi] pushed Qemu/Sbsa update by mistake
Date: Mon, 25 Nov 2024 17:09:52 +0000	[thread overview]
Message-ID: <CO1PR11MB4929718D584F1F38E886A6D7D22E2@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <6fe8521f-443d-4a2b-87fb-f79ad8cdbf0a@linaro.org>

If the commit is not correct, then you can revert the change and
push the revert commit.  

Since this is a public repo, forced pushes to remove the commit 
are now allowed.

Mike

> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Marcin
> Juszkiewicz via groups.io
> Sent: Monday, November 25, 2024 5:04 AM
> To: devel@edk2.groups.io
> Cc: Leif Lindholm <quic_llindhol@quicinc.com>
> Subject: [edk2-devel] [edk2-non-osi] pushed Qemu/Sbsa update by mistake
> 
> Hi
> 
> I prepared update of TF-A for QemuSbsa to bring it to v2.12 version.
> 
> Then misread my edk2-non-osi local repo setup and instead of pushing to
> fork, pushed to tianocore/edk2-non-osi repository directly.
> 
> Sorry.
> 
> 
> 
> 



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120835): https://edk2.groups.io/g/devel/message/120835
Mute This Topic: https://groups.io/mt/109770456/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-11-25 17:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 13:04 [edk2-devel] [edk2-non-osi] pushed Qemu/Sbsa update by mistake Marcin Juszkiewicz via groups.io
2024-11-25 17:09 ` Michael D Kinney via groups.io [this message]
2024-11-25 17:31   ` Ard Biesheuvel via groups.io

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=CO1PR11MB4929718D584F1F38E886A6D7D22E2@CO1PR11MB4929.namprd11.prod.outlook.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