Closed pinkforest closed 1 year ago
Thank you! Two things:
This can be audited with ... rsync :)
$ rsync -rcnv a/* b/
-r will recurse into the directories
-c will compare based on file checksum
-n will run it as a "dry run" and make no changes, but just print out the files
that would be updated
-v will print the output to stdout verbosely
e.g. like this:
git clone https://github.com/dalek-cryptography/curve25519-dalek.git
git clone https://github.com/dalek-cryptography/ed25519-dalek.git
git clone https://github.com/dalek-cryptography/x5519-dalek.git
pull this pr to "monorepo"
rsync -rcnv monorepo/curve25519-dalek/* curve25519-dalek/
rsync -rcnv monorepo/ed25519-dalek/* ed25519-dalek/
rsync -rcnv monorepo/x25519-dalek/* x25519-dalek/
Above without 'dry run" you can also do "git status" to see if any files changed and how they changed "git diff" if any.
Alright, made a pretty barebones README, but it should be OK for now imo. The dalek image doesn't load correctly anymore bc the URL is gonna change in this PR.
Ok - I had to re-organize our last commits since this PR needs a merge (not a squash) making it more difficult to change here (suggest doing more in follow-up PR's) and we have renames which need to be kept in separate commits in the middle. I gave you co-authored-by since I had to amend our last change commits on top.
Build's broken now but I have no idea what's causing it 😕
Something broke in transient dependency somewhere for the MSRV build - this should be mergeable in any case as this doesn't cause it.
Found what caused it - raised #538 to track it
As discussed this is the monorepo PR
ed25519
could haveed:
prefix and the PR links would be linked to old place - nonetheless this would be the tradeoff with history we would pay for easier consistency across the crates and usually the original commits has all the information from PR'sgit combine Procedure (see near last commits)