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
..
examples	working_copy: plumbing to propagate untracked paths to caller	2024-12-11 20:19:51 +09:00
src	working_copy: on snapshot, warn new large files and continue	2024-12-11 20:19:51 +09:00
testing	style: inline variables into format strings	2024-10-04 22:29:13 +02:00
tests	working_copy: on snapshot, warn new large files and continue	2024-12-11 20:19:51 +09:00
build.rs	build: fix cargo publish by symlinking cli/docs->docs	2024-11-05 17:37:14 -08:00
Cargo.toml	cargo: drop dependency on config crate	2024-12-10 16:08:50 +09:00
docs	build: fix cargo publish by symlinking cli/docs->docs	2024-11-05 17:37:14 -08:00
LICENSE	cargo: add LICENSE file to each crate we publish	2023-09-22 21:48:28 -07:00