Skip to content

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.

Copy link
Contributor

@nathan-contino nathan-contino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, ty

@nathan-contino nathan-contino merged commit 96f1aa5 into develop Jan 28, 2025
1 check passed
@nathan-contino nathan-contino deleted the lurch-patch-1 branch January 28, 2025 21:21
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.

3 participants