[PATCH 1/5] docs: mention "-k" for both forms of "git mv"
- From
Jeff King <peff@peff.net>
- Date
- Dec 12, 2011, 07:50 UTC
- Message-ID
- <20111212075031.GA17532@sigill.intra.peff.net>
- In-Reply-To
- <20111212074503.GB16511@sigill.intra.peff.net>
The "git mv" synopsis shows two forms: renaming a file, and moving files into a directory. They can both make use of the "-k" flag to ignore errors, so mention it in both places.
Signed-off-by: Jeff King <peff@peff.net> --- I can kind of see the rationale for the original content. Using "-k" is a lot more useful if you are actually doing multiple renames, so it makes more sense in the second form. But it is still useful in the first form as a shorthand for "git mv 2>/dev/null || true".
I actually would rather just see:
git mv [options] <source> <destination> git mv [options] <source>... <destination>
but if we are going to go that route, we should probably decide on a style and convert all of the descriptions at the same time.
Documentation/git-mv.txt | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-mv.txt b/Documentation/git-mv.txt index b8db373..4be7a71 100644 --- a/Documentation/git-mv.txt +++ b/Documentation/git-mv.txt @@ -15,7 +15,7 @@ DESCRIPTION ----------- This script is used to move or rename a file, directory or symlink. - git mv [-f] [-n] <source> <destination> + git mv [-f] [-n] [-k] <source> <destination> git mv [-f] [-n] [-k] <source> ... <destination directory> In the first form, it renames <source>, which must exist and be either
-- 1.7.8.13.g74677