milksad
/
rust-bitcoin-unsafe-fast
14
0
Fork 0
Code Issues Pull Requests Activity
rust-bitcoin-unsafe-fast/.gitignore

23 lines
368 B
Plaintext
Raw Normal View History

Update gitignore file Recently we introduced a workspace but did not update the git ignore file. Ignore lock files, build artifacts, test artifacts, and fuzz artifacts.
2022-09-16 02:13:13 +00:00
# .gitignore for rust-bitcoin repository workspace.
# Lock files
Add Cargo.lock to gitignore
2017-04-25 01:12:37 +00:00
Cargo.lock
Update gitignore file Recently we introduced a workspace but did not update the git ignore file. Ignore lock files, build artifacts, test artifacts, and fuzz artifacts.
2022-09-16 02:13:13 +00:00
internals/Cargo.lock
bitcoin/Cargo.lock
Import bitcoin_hashes crate into hashes We would like to bring the `bitcoin_hashes` crate into the `rust-bitcoin` repository. Import `bitcoin_hashes` into `rust-bitocin/hashes`, doing so looses all the commit history from the original crate but if we archive the original repository then the history will be preserved. We maintain the same version number obviously and in the changelog we note the change of repository. Commit hash that was tip of `bitcoin_hashes` at time of import: commit 54c16249e06cc6b7870c7fc07d90f489d82647c7 Includes making `embedded` and `fuzzing` per-crate i.e., move them into `bitcoin` as hashes includes these also. NOTE: Does _not_ enable fuzzing for `hashes` in CI. Notes on CI: Attempts to merge in the github actions from the hashes crate however reduces coverage by not running hashes tests for beta toolchain. Some additional work could be done to improve the CI to increase efficiency without reducing coverage. Leaving for another day.
2022-09-16 01:52:57 +00:00
hashes/Cargo.lock
Update gitignore file Recently we introduced a workspace but did not update the git ignore file. Ignore lock files, build artifacts, test artifacts, and fuzz artifacts.
2022-09-16 02:13:13 +00:00
# Build artifacts
target
internals/target
bitcoin/target
Import bitcoin_hashes crate into hashes We would like to bring the `bitcoin_hashes` crate into the `rust-bitcoin` repository. Import `bitcoin_hashes` into `rust-bitocin/hashes`, doing so looses all the commit history from the original crate but if we archive the original repository then the history will be preserved. We maintain the same version number obviously and in the changelog we note the change of repository. Commit hash that was tip of `bitcoin_hashes` at time of import: commit 54c16249e06cc6b7870c7fc07d90f489d82647c7 Includes making `embedded` and `fuzzing` per-crate i.e., move them into `bitcoin` as hashes includes these also. NOTE: Does _not_ enable fuzzing for `hashes` in CI. Notes on CI: Attempts to merge in the github actions from the hashes crate however reduces coverage by not running hashes tests for beta toolchain. Some additional work could be done to improve the CI to increase efficiency without reducing coverage. Leaving for another day.
2022-09-16 01:52:57 +00:00
hashes/target
Update gitignore file Recently we introduced a workspace but did not update the git ignore file. Ignore lock files, build artifacts, test artifacts, and fuzz artifacts.
2022-09-16 02:13:13 +00:00
# Test artifacts
bitcoin/dep_test
add IntelliJ IDEA files
2018-02-28 09:37:26 +00:00
Update gitignore file Recently we introduced a workspace but did not update the git ignore file. Ignore lock files, build artifacts, test artifacts, and fuzz artifacts.
2022-09-16 02:13:13 +00:00
# Fuzz artifacts
Import bitcoin_hashes crate into hashes We would like to bring the `bitcoin_hashes` crate into the `rust-bitcoin` repository. Import `bitcoin_hashes` into `rust-bitocin/hashes`, doing so looses all the commit history from the original crate but if we archive the original repository then the history will be preserved. We maintain the same version number obviously and in the changelog we note the change of repository. Commit hash that was tip of `bitcoin_hashes` at time of import: commit 54c16249e06cc6b7870c7fc07d90f489d82647c7 Includes making `embedded` and `fuzzing` per-crate i.e., move them into `bitcoin` as hashes includes these also. NOTE: Does _not_ enable fuzzing for `hashes` in CI. Notes on CI: Attempts to merge in the github actions from the hashes crate however reduces coverage by not running hashes tests for beta toolchain. Some additional work could be done to improve the CI to increase efficiency without reducing coverage. Leaving for another day.
2022-09-16 01:52:57 +00:00
bitcoin/fuzz/hfuzz_target
bitcoin/fuzz/hfuzz_workspace
hashes/fuzz/hfuzz_target
hashes/fuzz/hfuzz_workspace