Yuya Nishihara 168c7979fe working_copy: on snapshot, warn new large files and continue ... I think this provides a better UX than refusing any operation due to large files. Because untracked files won't be overwritten, it's usually safe to continue operation ignoring the untracked files. One caveat is that new large files can become tracked if files of the same name checked out. (see the test case) FWIW, the warning will be printed only once if watchman is enabled. If we use the snapshot stats to print untracked paths in "jj status", this will be a problem. Closes #3616, #3912		2024-12-11 20:19:51 +09:00
..
benches	style: add semicolon at the end of expressions used as statements	2024-10-04 22:29:13 +02:00
gen-protos	cargo: inherit lints configuration from workspace	2024-10-04 22:29:13 +02:00
proc-macros	style: remove useless uses of .iter()	2024-10-04 22:29:13 +02:00
src	working_copy: on snapshot, warn new large files and continue	2024-12-11 20:19:51 +09:00
tests	working_copy: on snapshot, warn new large files and continue	2024-12-11 20:19:51 +09:00
testutils	working_copy: plumbing to propagate untracked paths to caller	2024-12-11 20:19:51 +09:00
Cargo.toml	cargo: drop dependency on config crate	2024-12-10 16:08:50 +09:00
LICENSE