Martin von Zweigbergk 8ce099470b cargo: explicitly indicate paths to publish ... Running `cargo publish` from a non-colocated repo (such as my usual repo) is currently quite scary because it uploads all non-hidden files, even if they're ignored by `.gitignore` (https://github.com/rust-lang/cargo/issues/2063). I noticed this a while ago and have always run the command from a fresh clone since then. To avoid the need for that, let's use the workaround mentioned on the bug, which is to explicitly list patterns we want to publish.		2024-04-15 20:37:00 -07:00
..
examples	cli_util: support multiple extensions consistently	2024-04-12 14:07:33 -04:00
src	Fix empty files can't be selected in the builtin diff editor	2024-04-15 23:28:06 -04:00
testing	revset: add support for file(kind:pattern) syntax	2024-04-07 19:43:29 +09:00
tests	cli: migrate "cat" to matcher API, warn unmatched paths	2024-04-16 10:12:31 +09:00
build.rs
Cargo.toml	cargo: explicitly indicate paths to publish	2024-04-15 20:37:00 -07:00
LICENSE