public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: Ard Biesheuvel <ardb@kernel.org>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] Merge commit in edk2-non-osi
Date: Wed, 21 Feb 2024 15:05:18 +0000	[thread overview]
Message-ID: <SA2PR11MB4938219C5E587AD59927AD63D2572@SA2PR11MB4938.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAMj1kXG2VtH=dKU6FEd_nQC95Y5U+_k8UJB6BrThNnr_sMu1Mw@mail.gmail.com>

Hi Ard,

I disagree.  We have never allowed a force push to the main
branch of TianoCore repos.  This has happened before and
was discussed and the policy is to not fix.  Even the edk2
repo has some merge commits in its history that were discussed
and not fixed.

We can never know how many downstream consumers are syncing
with main branches.

Mike

> -----Original Message-----
> From: Ard Biesheuvel <ardb@kernel.org>
> Sent: Wednesday, February 21, 2024 12:07 AM
> To: devel@edk2.groups.io; Desimone, Nathaniel L
> <nathaniel.l.desimone@intel.com>
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>
> Subject: Re: [edk2-devel] Merge commit in edk2-non-osi
> 
> On Wed, 21 Feb 2024 at 02:49, Nate DeSimone
> <nathaniel.l.desimone@intel.com> wrote:
> >
> > Hi Everyone,
> >
> > It appears that a merge commit was introduced to edk2-non-osi due to
> a PR merge:
> >
> > https://github.com/tianocore/edk2-non-
> osi/commit/61b65fccfe4c75bc9ecb7b542412a436e3db5de6
> >
> > I would like to remind everyone that we generally don't accept
> submissions via PRs yet. At the very least please click "Rebase and
> merge" when closing the PR instead of "Merge pull request". Since that
> merge commit is currently at the top of the tree, can we delete it?
> >
> 
> 
> I think force rebasing is fine in this particular case - the file
> contents will remain the same, it is just the git history that gets
> linearized, so everyone that pulls from it should get the expected
> results.


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



  reply	other threads:[~2024-02-21 15:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21  1:49 [edk2-devel] Merge commit in edk2-non-osi Nate DeSimone
2024-02-21  8:06 ` Ard Biesheuvel
2024-02-21 15:05   ` Michael D Kinney [this message]
2024-02-21 23:29     ` Ard Biesheuvel
2024-02-21 23:42       ` Nate DeSimone
2024-02-21  8:57 ` Marcin Juszkiewicz
2024-02-21 15:26   ` Michael D Kinney

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=SA2PR11MB4938219C5E587AD59927AD63D2572@SA2PR11MB4938.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