abdul124
/
rust-core_io
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Rust std::io with all the parts that don't work in core removed.
75 Commits 7 Branches 1 Tag 830 KiB
RenderScript 92.1%
Shell 4.7%
Rust 3.2%
Go to file
bors[bot] 2c0030ac9a Merge #28 
28: Update to 2019-07-01 r=jethrogb a=jethrogb

bors r+

Co-authored-by: Jethro Beekman <jethro@fortanix.com>
 		2019-07-01 16:08:33 +00:00
patches Update to 2019-07-01 2019-07-01 09:07:40 -07:00
src Address review comments 2019-06-06 19:46:25 -07:00
.gitignore Keep track of individual patches instead of patched source versions 2016-10-31 00:13:22 -07:00
.travis.yml Parse mapping.rs manually, fix CI versions. 2019-04-30 18:27:50 -07:00
Cargo.toml Update to 2019-07-01 2019-07-01 09:07:40 -07:00
LICENSE-APACHE Add some documentation and copyright info 2016-07-10 13:45:57 -07:00
LICENSE-MIT Add some documentation and copyright info 2016-07-10 13:45:57 -07:00
README.md Setup Travis CI 2019-04-30 16:43:18 -07:00
build-src.sh Address review comments 2019-04-30 18:55:16 -07:00
build.rs Address review comments 2019-06-06 19:46:25 -07:00
ct.sh Update to 2019-07-01 2019-07-01 09:07:40 -07:00
doc.sh Add collections/alloc features 2016-07-10 13:45:57 -07:00
edit-patches.sh Additional macOS fixes 2019-04-27 12:56:47 -07:00
functions.sh Address review comments 2019-04-30 18:55:16 -07:00
mapping.rs Update to 2019-07-01 2019-07-01 09:07:40 -07:00
publish.sh Add publish script 2016-11-02 22:43:30 -07:00

README.md

core_io

Build Status

std::io with all the parts that don't work in core removed.

Adding new nightly versions

First, make sure the commit you want to add is fetch in the git tree at /your/rust/dir/.git. Then, import the right source files:

$ echo FULL_COMMIT_ID ...|GIT_DIR=/your/rust/dir/.git ./build-src.sh

Instead of echoing in the commit IDs, you might pipe in rustc-commit-db list-valid.

The build-src script will prompt you to create patches for new commits. You will be dropped in a shell prompt with a temporary new, clean, git repository just for this patch. Make any changes necessary to make it build. Don't commit any changes! When exiting the shell and the script will use the working tree diff as the patch. The temporary git repository will be deleted. Before dropping into the shell, the script will show you nearby commits, you can try to apply $PATCH_DIR/that_commit.patch and see if it works for you.

Publishing

$ echo FULL_COMMIT_ID ...|GIT_DIR=/your/rust/dir/.git ./build-src.sh publish

Again, instead of echoing in the commit IDs, you might pipe in rustc-commit-db list-valid.

Editing patches

To edit all patches, again make a checkout of the rust source. Then, run:

$ GIT_DIR=/your/rust/dir/.git ./edit-patches.sh

The script will prompt you to make changes. You will be dropped in a shell prompt with a temporary new, clean, git repository just for this patch edit. The original patch will be the HEAD commit in the repository. Make any changes you want. Don't commit any changes! When exiting the shell and the script will use the diff between the working tree and the root commit as the patch. The temporary git repository will be deleted. When editing further commits, the previous patch changes will already be applied to the working tree (if succesful).