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.

Sign up for GitHub

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

Jump to bottom

Switch to big endian #28

Closed
larseggert opened this issue Nov 26, 2016 · 4 comments
Closed

Switch to big endian #28

larseggert opened this issue Nov 26, 2016 · 4 comments
Assignees
@martinthomson @janaiyengar
Labels
-transport design An issue that affects the design of the protocol; resolution requires consensus. has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list.

Comments

@larseggert
Copy link
Member

larseggert commented Nov 26, 2016 •
edited
Loading

We had consensus in Seoul (which we should reconfirm on the list) about switching from little endian to big endian. This should probably happen in concert with the version number scheme that @martinthomson and @janaiyengar are hashing out.
@martinthomson martinthomson added design An issue that affects the design of the protocol; resolution requires consensus. editor-ready labels Nov 28, 2016
@larseggert
Copy link
Member Author

I started an email thread to confirm the consensus. Deadline Jan 6, 2017.

martinthomson added a commit that referenced this issue Jan 4, 2017
@martinthomson
Big endian
b5823a5 
Closes #28
@martinthomson martinthomson mentioned this issue Jan 4, 2017
Merged
janaiyengar pushed a commit that referenced this issue Jan 5, 2017
@martinthomson
Big endian
44f1e18 
Closes #28
@mnot
Copy link
Member

mnot commented Jan 5, 2017

@janaiyengar please don't close design issues, we need to complete the call for consensus.

@mnot mnot reopened this Jan 5, 2017
@janaiyengar
Copy link
Contributor

Ah, apologies. I thought we had already wrapped up the consensus call -- I merged the PR, which automagically closed the issue. I'm happy to revert the (now merged) PR if consensus changes.

@larseggert
Copy link
Member Author

larseggert commented Jan 11, 2017 •
edited
Loading

As @martinthomson just noted in email, the consensus call has ended. Will send email to the group now.

@mnot mnot added has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list. and removed editor-ready labels Mar 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@martinthomson martinthomson

@janaiyengar janaiyengar

Labels
-transport design An issue that affects the design of the protocol; resolution requires consensus. has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@martinthomson @mnot @larseggert @janaiyengar