-
Notifications
You must be signed in to change notification settings - Fork 35
Release 0.6.1 #50
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
Release 0.6.1 #50
Conversation
|
|
||
| name = "spidev" | ||
| version = "0.6.0" | ||
| version = "0.6.2-alpha.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks wrong for the 0.6.1 release. Or am I somehow misunderstanding the release process?
| version = "0.6.2-alpha.0" | |
| version = "0.6.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah ok, that wasn't obvious when viewing the changes.
So this MR should be merged in "rebase and merge" mode, because "squash and merge" would destroy the intermediate commit, and the default mode "merge pull request" would create a slightly confusing commit history, right?
ee8a1e5 to
4c960d2
Compare
|
Rebased this PR onto #52. |
The linux-embedded-hal exposes spidev and in order to fix rust-embedded/linux-embedded-hal#120, we need a patch release for 0.6. I already created the branch maintenance-0.6 and this PR backports #49 onto 0.6 and prepares release 0.6.1.