Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ArmPkg: Fix various typos #143

Closed
wants to merge 1 commit into from
Closed

Conversation

Coeur
Copy link
Contributor

@Coeur Coeur commented Jun 27, 2019

Meta

This is an experimental pull request, as discussed many times on the edk2 mailing-list.
It is:

  • an easy pull request
  • a non-urgent pull request

It fits the experiment of using a GitHub pull request over a mailing-list patch.

Once reviewed and approved, the maintainer of this repo (edk2) has multiple possibilities to handle it:

  • either use command line to rebase/merge/etc. this pull request (git pull https://github.com/coeur/edk2.git Typo-ArmPkg)
  • either use the GitHub interface and choose to rebase (or merge or squash): Screen Shot 2019-06-27 at 12 24 32 PM

Pull Request

This is actually a cherry pick for ArmPkg only from a larger change updated since 2018 at Coeur@1ee272d.

Fix various typos in ArmPkg.

Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Coeur <coeur@gmx.fr>
@lersek
Copy link
Member

lersek commented Jun 27, 2019

Antoine, I'll have to reject this github PR (similarly to other github pull requests for the edk2 project). While we may have discussed github pull requests for other projects on the list, such as "Edk2-Library", to my knowledge we're not even considering an evaluation of github pull requests for the main edk2 project. Please submit your patch to the list for review. The point is exactly that patch review happen on the list. Thanks.

@lersek
Copy link
Member

lersek commented Jun 27, 2019

For the record, a few months ago we did evaluate github, phabricator, and gitlab. Gerrit was added to the "evaluation backlog". From the three we checked, at that time, github proved the least inferior to the mailing list. We identified a number of sticking points which github.com should address before we could consider adopting it.

http://mid.mail-archive.com/793375cd-f55a-fa22-97c2-d6fd04da7d8b@linux.intel.com
http://mid.mail-archive.com/0b2ce1b0-93ab-aef2-d192-23fd84024b70@redhat.com

(Alternative links:

https://lists.01.org/pipermail/edk2-devel/2019-February/036428.html
https://lists.01.org/pipermail/edk2-devel/2018-December/033509.html
)

Nothing has changed since, to my knowledge, so I don't see a reason to reopen the investigation.

@Coeur
Copy link
Contributor Author

Coeur commented Jun 27, 2019

:(

kuqin12 pushed a commit to kuqin12/edk2 that referenced this pull request Nov 29, 2022
…ianocore#143)

## Description

The variable used to check if we added entries to the memory map should
be MemoryMapEnd, not MapEntryEnd.

## Breaking change?
No

## How This Was Tested

Testing special regions

## Integration Instructions

N/A
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants