From 4b92a512189e35c86491221ccc14c2e951936c4e Mon Sep 17 00:00:00 2001 From: kopp Date: Mon, 19 Feb 2024 00:55:27 +0100 Subject: [PATCH] fix: use --override rather than -o to specify overrides in README.md (#1668) ## Summary Fix documentation (Readme.md): `-o` is the short for `--output-file`, so using `-o overrides.txt` would store the output in `overrides.txt` rather than using that as overrides. ## Test Plan no tests for docs (yet?) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c07fe4a83..135a65242 100644 --- a/README.md +++ b/README.md @@ -275,7 +275,7 @@ Historically, `pip` has supported "constraints" (`-c constraints.txt`), which al narrow the set of acceptable versions for a given package. uv supports constraints, but also takes this concept further by allowing users to _override_ the -acceptable versions of a package across the dependency tree via overrides (`-o overrides.txt`). +acceptable versions of a package across the dependency tree via overrides (`--override overrides.txt`). In short, overrides allow the user to lie to the resolver by overriding the declared dependencies of a package. Overrides are a useful last resort for cases in which the user knows that a