You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 21, 2018. It is now read-only.
So long yak hair short, I wanted to be able to see if a particular commit to cargo was shipped with a particular released version of rustc. Unless I'm missing something, this information isn't straightforward to find anywhere!
I got really excited when I saw the cargo-revs.txt file in this repo, though, finally! Here it is! The git rev SHAs that were shipped with rustc! Oh wait-- it's only the date of the nightly that was used :( :( :( Which isn't always the last commit on that date...
So then I found the nightly cargo trigger of buildbot's, went to the build for a particular date (say, 2016-08-21) and that page says "got revision 109cb7c33d426044d141457049bd0fffaca1327c" which matches what I see if I do rustup default beta (since beta is 1.12.0 right now) and say cargo --version: cargo 0.13.0-nightly (109cb7c 2016-08-19).
I did that with other versions until buildbot ran out of builds to give me (it looks like it only keeps the last 500), so I think I have the correct SHAs.
Even though rust-packaging doesn't need these revs, would it be terrible to include them in cargo-revs.txt for future human reference and parse them out and have the code ignore them?
I'm also about to open an issue with cargo about tagging these commits with something to indicate the rustc version they went with, so if that seems like a better solution then feel free to close this :)
Here's the SHAs that I found and the buildbot source links, let me know if you'd like a PR in any particular format if you're in favor of this!
I believe you can get the cargo sha for a particular revision of rustc out of the manifest files at e.g. https://static.rust-lang.org/dist/2016-09-27/channel-rust-nightly.toml. Somewhere in there is information about the associated cargo package, and I believe the cargo version number and commit sha.
So long yak hair short, I wanted to be able to see if a particular commit to cargo was shipped with a particular released version of rustc. Unless I'm missing something, this information isn't straightforward to find anywhere!
I got really excited when I saw the cargo-revs.txt file in this repo, though, finally! Here it is! The git rev SHAs that were shipped with rustc! Oh wait-- it's only the date of the nightly that was used :( :( :( Which isn't always the last commit on that date...
So then I found the nightly cargo trigger of buildbot's, went to the build for a particular date (say, 2016-08-21) and that page says "got revision 109cb7c33d426044d141457049bd0fffaca1327c" which matches what I see if I do
rustup default beta
(since beta is 1.12.0 right now) and saycargo --version
: cargo 0.13.0-nightly (109cb7c 2016-08-19).I did that with other versions until buildbot ran out of builds to give me (it looks like it only keeps the last 500), so I think I have the correct SHAs.
Even though rust-packaging doesn't need these revs, would it be terrible to include them in cargo-revs.txt for future human reference and parse them out and have the code ignore them?
I'm also about to open an issue with cargo about tagging these commits with something to indicate the rustc version they went with, so if that seems like a better solution then feel free to close this :)
Here's the SHAs that I found and the buildbot source links, let me know if you'd like a PR in any particular format if you're in favor of this!
The text was updated successfully, but these errors were encountered: