Skip to content

Conversation

@gkelly
Copy link
Contributor

@gkelly gkelly commented May 14, 2020

A pair of changes (rust-embedded/svd#119, rust-embedded/svd2rust#444)
recently went into the svd2rust and svd-parser crates. Until these
changes are part of a release have update.sh pull a fork of svd2rust
that uses the master version of svd-parser.

See #195.

A pair of changes (rust-embedded/svd#119, rust-embedded/svd2rust#444)
recently went into the `svd2rust` and `svd-parser` crates that improves
the handling of cluster names and the generation of full type paths for
cluster instances. Until these changes are part of a release have
`update.sh` pull a fork of `svd2rust` that uses the master version of
`svd-parser`.

See atsamd-rs#195.
@gkelly gkelly force-pushed the bleeding-edge-svd2rust branch from e9a405b to 2b84214 Compare May 14, 2020 01:27
@sajattack
Copy link
Member

Could you maybe pin the commit hash so we don't get other unexpected bleeding edge changes?

Ensure that changes in the upstream gkelly/svd2rust repository don't end
up accidentially included during normal use by pinning to a specific
revision.
@gkelly
Copy link
Contributor Author

gkelly commented May 16, 2020

Just pushed a commit that pins svd2rust to gkelly/svd2rust@2bbb605, which itself includes an explicit rev for rust-embedded/svd, so no change in either repository can get accidentally used.

@gkelly gkelly mentioned this pull request May 16, 2020
8 tasks
@sajattack sajattack merged commit 0035a81 into atsamd-rs:master May 16, 2020
@gkelly gkelly deleted the bleeding-edge-svd2rust branch May 16, 2020 19:09
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