doc(stash): clarify the description of `save`
The original phrasing of this paragraph made at least one person stumble over the word "from" (thinking that it was a typo and "from" was intended), and other readers chimed in, agreeing that it was confusing: https://public-inbox.org/git/0102016b8d597569-c1f6cfdc-cb45-4428-8737-cb1bc30655d8-000000@eu-west-1.amazonses.com/#t Let's rewrite that paragraph for clarity. Inspired-by-a-patch-by: Catalin Criste <cris_linu_w@yahoo.com> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Johannes Schindelin committed
Oct 10, 2019 at 03:06 UTC
57d8f4b4c71fe422ea3fe6d79d3e121426b46f5a
1 file changed
+3
-2
Documentation/git-stash.txt
+3
-2
@@ -87,8 +87,9 @@ The `--patch` option implies `--keep-index`. You can use
87
save [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [<message>]::
88
89
This option is deprecated in favour of 'git stash push'. It
90
- differs from "stash push" in that it cannot take pathspecs,
91
- and any non-option arguments form the message.
90
+ differs from "stash push" in that it cannot take pathspecs.
91
+ Instead, all non-option arguments are concatenated to form the stash
92
+ message.
93
94
list [<options>]::
95