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

Re-order big table in revision-codes.adoc #4015

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

Conversation

lurch
Copy link
Contributor

@lurch lurch commented Jan 24, 2025

The current order is semi-random because some people have added new Pis by alphabetical revision-code, and some people have added new Pis to the bottom of the list. So to solve any conflicts, make it explicitly newest-Pi-at-bottom.

The revision-codes table is now sorted by Type (from the preceding table), then Revision, then RAM, and finally Code. This is the most likely order-of-manufacture, which means we'll normally just add new revision-codes to the very bottom of the table, without having to worry about re-ordering entries.

See comments in #4013

Ping @JamesH65 and @nathan-contino (I won't be upset if you decide to reject this).

Make it explicitly newest-Pi-at-bottom
@JamesH65
Copy link
Contributor

There was never any implicit ordering in the past so I have no preferences one way or another.

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.

2 participants