stash: support pathspec argument
A message that is not in the archive (sent off-list or not yet received): mailto:[email protected]
v4 cover stash: support pathspec argument
Thanks Peff and Junio for the review of the last round.
Changes since v3:
- Instead of using ${1-...} to check for missing arguments and dying show the usage for stash instead, being more consistent with how the rest of stash behaves
- Let push_stash handle the --help argument from save_stash as well, passing it through directly.
- Fix the tests to not pipe the output to something, and thereby swallowing the error codes
- Update the commit message in 4/7 to acknowledge that there is a small regression between the two versions
- Correctly detect when there are no changes, and only show the message once
- Fix the accidental deletion of untracked files when a pathspec is used. Also added test cases for that.
- Add documentation for git stash push to the usage text
- Respect the -q flag and the GIT_QUIET environment variable
- This also adds two new patches, one using push_stash instead of save_stash for git stash without any verb. The other allows using a pathspec in the verb-less option of git stash.
Interdiff below:
Documentation/git-stash.txt +5 -5
@@ -13,15 +13,15 @@ SYNOPSIS 'git stash' drop [-q|--quiet] [<stash>] 'git stash' ( pop | apply ) [--index] [-q|--quiet] [<stash>] 'git stash' branch <branchname> [<stash>] -'git stash' [save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] - [-u|--include-untracked] [-a|--all] [<message>]] -'git stash' push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] +'git stash' save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [<message>] +'git stash' [push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] [-u|--include-untracked] [-a|--all] [-m|--message <message>]] - [--] [<pathspec>...] + [--] [<pathspec>...]] 'git stash' clear 'git stash' create [<message>] 'git stash' create [-m <message>] [-u|--include-untracked <untracked|all>] - [-- <paths>...] + [-- <pathspec>...] 'git stash' store [-m|--message <message>] [-q|--quiet] <commit> DESCRIPTION
git-stash.sh +36 -21
133 lines not on this page · raw message
t/t3903-stash.sh +57 -14
112 lines not on this page · raw message
t/t3905-stash-include-untracked.sh +5 -5
@@ -197,16 +197,16 @@ test_expect_success 'stash push --include-untracked with pathspec' ' ' test_expect_success 'stash push with $IFS character' ' - >"foo bar" && + >"foo bar" && >foo && >bar && git add foo* && - git stash push --include-untracked -- foo* && - test_path_is_missing "foo bar" && - test_path_is_missing foo && + git stash push --include-untracked -- "foo b*" && + test_path_is_missing "foo bar" && + test_path_is_file foo && test_path_is_file bar && git stash pop && - test_path_is_file "foo bar" && + test_path_is_file "foo bar" && test_path_is_file foo && test_path_is_file bar '
Thomas Gummerer (7):
Documentation/stash: remove mention of git reset --hard
stash: introduce push verb
stash: add test for the create command line arguments
stash: introduce new format create
stash: teach 'push' (and 'create') to honor pathspec
stash: use stash_push for no verb form
stash: allow pathspecs in the no verb form
Documentation/git-stash.txt | 21 ++++- git-stash.sh | 157 +++++++++++++++++++++++++++++++------ t/t3903-stash.sh | 127 +++++++++++++++++++++++++++++- t/t3905-stash-include-untracked.sh | 26 ++++++ 4 files changed, 302 insertions(+), 29 deletions(-)
Signature · 1 line
2.11.0.301.g86e6ecc671.dirty
PATCH v4 1/7 Documentation/stash: remove mention of git reset --hard
Don't mention git reset --hard in the documentation for git stash save. It's an implementation detail that doesn't matter to the end user and thus shouldn't be exposed to them. In addition it's not quite true for git stash -p, and will not be true when a filename argument to limit the stash to a few files is introduced.
--- Documentation/git-stash.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
Documentation/git-stash.txt +3 -2
@@ -47,8 +47,9 @@ OPTIONS save [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [<message>]:: - Save your local modifications to a new 'stash', and run `git reset - --hard` to revert them. The <message> part is optional and gives + Save your local modifications to a new 'stash' and roll them + back to HEAD (in the working tree and in the index). + The <message> part is optional and gives the description along with the stashed state. For quickly making a snapshot, you can omit _both_ "save" and <message>, but giving only <message> does not trigger this action to prevent a misspelled
Signature · 1 line
2.11.0.301.g86e6ecc671.dirty
PATCH v4 2/7 stash: introduce push verb
In reply to Thomas GummererIntroduce a new git stash push verb in addition to git stash save. The push verb is used to transition from the current command line arguments to a more conventional way, in which the message is given as an argument to the -m option.
This allows us to have pathspecs at the end of the command line arguments like other Git commands do, so that the user can say which subset of paths to stash (and leave others behind).
--- git-stash.sh | 46 +++++++++++++++++++++++++++++++++++++++++++--- t/t3903-stash.sh | 9 +++++++++ 2 files changed, 52 insertions(+), 3 deletions(-)
git-stash.sh +43 -3
@@ -9,6 +9,8 @@ USAGE="list [<options>] or: $dashless branch <branchname> [<stash>] or: $dashless [save [--patch] [-k|--[no-]keep-index] [-q|--quiet] [-u|--include-untracked] [-a|--all] [<message>]] + or: $dashless push [--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [-m <message>] or: $dashless clear" SUBDIRECTORY_OK=Yes
@@ -189,10 +191,11 @@ store_stash () { return $ret } -save_stash () { +push_stash () { keep_index= patch_mode= untracked= + stash_msg= while test $# != 0 do case "$1" in
@@ -216,6 +219,11 @@ save_stash () { -a|--all) untracked=all ;; + -m|--message) + shift + test -z ${1+x} && usage + stash_msg=$1 + ;; --help) show_help ;;
@@ -251,8 +259,6 @@ save_stash () { die "$(gettext "Can't use --patch and --include-untracked or --all at the same time")" fi - stash_msg="$*" - git update-index -q --refresh if no_changes then
@@ -291,6 +297,36 @@ save_stash () { fi } +save_stash () { + push_options= + while test $# != 0 + do + case "$1" in + --) + shift + break + ;; + -*) + # pass all options through to push_stash + push_options="$push_options $1" + ;; + *) + break + ;; + esac + shift + done + + stash_msg="$*" + + if test -z "$stash_msg" + then + push_stash $push_options + else + push_stash $push_options -m "$stash_msg" + fi +} + have_stash () { git rev-parse --verify --quiet $ref_stash >/dev/null }
@@ -617,6 +653,10 @@ save) shift save_stash "$@" ;; +push) + shift + push_stash "$@" + ;; apply) shift apply_stash "$@"
t/t3903-stash.sh +9 -0
@@ -775,4 +775,13 @@ test_expect_success 'stash is not confused by partial renames' ' test_path_is_missing file ' +test_expect_success 'push -m shows right message' ' + >foo && + git add foo && + git stash push -m "test message" && + echo "stash@{0}: On master: test message" >expect && + git stash list -1 >actual && + test_cmp expect actual +' + test_done
Signature · 1 line
2.11.0.301.g86e6ecc671.dirty
PATCH v4 3/7 stash: add test for the create command line arguments
In reply to Thomas GummererCurrently there is no test showing the expected behaviour of git stash create's command line arguments. Add a test for that to show the current expected behaviour and to make sure future refactorings don't break those expectations.
--- t/t3903-stash.sh | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+)
t/t3903-stash.sh +18 -0
@@ -784,4 +784,22 @@ test_expect_success 'push -m shows right message' ' test_cmp expect actual ' +test_expect_success 'create stores correct message' ' + >foo && + git add foo && + STASH_ID=$(git stash create "create test message") && + echo "On master: create test message" >expect && + git show --pretty=%s -s ${STASH_ID} >actual && + test_cmp expect actual +' + +test_expect_success 'create with multiple arguments for the message' ' + >foo && + git add foo && + STASH_ID=$(git stash create test untracked) && + echo "On master: test untracked" >expect && + git show --pretty=%s -s ${STASH_ID} >actual && + test_cmp expect actual +' + test_done
Signature · 1 line
2.11.0.301.g86e6ecc671.dirty
PATCH v4 4/7 stash: introduce new format create
In reply to Thomas Gummerergit stash create currently supports a positional argument for adding a message. This is not quite in line with how git commands usually take comments (using a -m flag).
Add a new syntax for adding a message to git stash create using a -m flag. This is with the goal of deprecating the old style git stash create with positional arguments.
This also adds a -u argument, for untracked files. This is already used internally as another positional argument, but can now be used from the command line.
This introduces a slight regression, when git stash create -m works is used. Before this change, it created a stash with the message "-m works", but now it creates a stash with the message "-m".
--- Documentation/git-stash.txt | 1 + git-stash.sh | 52 +++++++++++++++++++++++++++++++++++++++++---- t/t3903-stash.sh | 9 ++++++++ 3 files changed, 58 insertions(+), 4 deletions(-)
Documentation/git-stash.txt +1 -0
@@ -17,6 +17,7 @@ SYNOPSIS [-u|--include-untracked] [-a|--all] [<message>]] 'git stash' clear 'git stash' create [<message>] +'git stash' create [-m <message>] [-u|--include-untracked <untracked|all>] 'git stash' store [-m|--message <message>] [-q|--quiet] <commit> DESCRIPTION
git-stash.sh +48 -4
70 lines not on this page · raw message
t/t3903-stash.sh +9 -0
@@ -802,4 +802,13 @@ test_expect_success 'create with multiple arguments for the message' ' test_cmp expect actual ' +test_expect_success 'new style stash create stores correct message' ' + >foo && + git add foo && + STASH_ID=$(git stash create -m "create test message new style") && + echo "On master: create test message new style" >expect && + git show --pretty=%s -s ${STASH_ID} >actual && + test_cmp expect actual +' + test_done
Signature · 1 line
2.11.0.301.g86e6ecc671.dirty
A message that is not in the archive (sent off-list or not yet received): [email protected]
Re: [PATCH v4 4/7] stash: introduce new format create
Quoted 76 lines · Matthieu Moy
Quoted 27 lines · Thomas Gummerer
create_stash() {git-stash.sh +24
-2- stash_msg="$1" - untracked="$2" + stash_msg= + untracked= + new_style= + while test $# != 0 + do + case "$1" in + -m|--message) + shift + test -z ${1+x} && usage + stash_msg="$1" + new_style=t + ;; + -u|--include-untracked) + shift + test -z ${1+x} && usage + untracked="$1" + new_style=t + ;; + *) + if test -n "$new_style" + then + echo "invalid argument" + option="$1" + # TRANSLATORS: $option is an invalid option, likegit-stash.sh clear_stash () { · line 94
Quoted 10 lines
git-stash.sh +10
-0+ # `--blah-blah'. The 7 spaces at the beginning of the + # second line correspond to "error: ". So you should line + # up the second line with however many characters the + # translation of "error: " takes in your language. E.g. in + # English this is: + # + # $ git stash save --blah-blah 2>&1 | head -n 2 + # error: unknown option for 'stash save': --blah-blah + # To provide a message, use git stash save -- '--blah-blah' + eval_gettextln "error: unknown option for 'stash create': \$option"The TRANSLATORS: hint seems a typoed cut-and-paste from somewhere else. There are no 7 spaces in this message.
Actually, if I read the code correctly, $option is not even necessarily an option as you're matching *. Perhaps you meant something like
-*)
option="$1"
# TRANSLATORS: $option is an invalid option, like
# `--blah-blah'. The 7 spaces at the beginning of the
# second line correspond to "error: ". So you should line
# up the second line with however many characters the
# translation of "error: " takes in your language. E.g. in # English this is:
#
# $ git stash save --blah-blah 2>&1 | head -n 2
# error: unknown option for 'stash save': --blah-blah
# To provide a message, use git stash save -- '--blah-blah'
eval_gettextln"error: unknown option for 'stash save': \$option
To provide a message, use git stash save -- '\$option'"
usage
;;
*)
if test -n "$new_style"
then
arg="$1"
eval_gettextln"error: invalid argument for 'stash create': \$arg" usage
fi
break
;;(untested)
Also, you may want to guard against
Quoted 8 lines
git stash create "some message" -m "some other message"
since you are already rejecting
git stash create -m "some message" "some other message"
? Or perhaps apply "last one wins" for both "-m message" and "message"-without-dash-m.
Thanks, you're right I was missing some cases here. As I just indicated in [1] however I think we can just make this an internal interface, instead of user interface facing, so I think we'll need less error checking.
Quoted 3 lines
Signature · 2 lines
Matthieu Moy http://www-verimag.imag.fr/~moy/
PATCH v4 5/7 stash: teach 'push' (and 'create') to honor pathspec
In reply to Thomas GummererWhile working on a repository, it's often helpful to stash the changes of a single or multiple files, and leave others alone. Unfortunately git currently offers no such option. git stash -p can be used to work around this, but it's often impractical when there are a lot of changes over multiple files.
Allow 'git stash push' to take pathspec to specify which paths to stash.
--- Documentation/git-stash.txt | 11 ++++++ git-stash.sh | 50 ++++++++++++++++++++------ t/t3903-stash.sh | 72 ++++++++++++++++++++++++++++++++++++++ t/t3905-stash-include-untracked.sh | 26 ++++++++++++++ 4 files changed, 148 insertions(+), 11 deletions(-)
Documentation/git-stash.txt +11 -0
@@ -15,9 +15,13 @@ SYNOPSIS 'git stash' branch <branchname> [<stash>] 'git stash' [save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] [-u|--include-untracked] [-a|--all] [<message>]] +'git stash' push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [-m|--message <message>]] + [--] [<pathspec>...] 'git stash' clear 'git stash' create [<message>] 'git stash' create [-m <message>] [-u|--include-untracked <untracked|all>] + [-- <pathspec>...] 'git stash' store [-m|--message <message>] [-q|--quiet] <commit> DESCRIPTION
@@ -47,6 +51,7 @@ OPTIONS ------- save [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [<message>]:: +push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [-m|--message <message>] [--] [<pathspec>...]:: Save your local modifications to a new 'stash' and roll them back to HEAD (in the working tree and in the index).
@@ -56,6 +61,12 @@ save [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q only <message> does not trigger this action to prevent a misspelled subcommand from making an unwanted stash. + +When pathspec is given to 'git stash push', the new stash records the +modified states only for the files that match the pathspec. The index +entries and working tree files are then rolled back to the state in +HEAD only for these files, too, leaving files that do not match the +pathspec intact. ++ If the `--keep-index` option is used, all changes already added to the index are left intact. +
git-stash.sh +39 -11
122 lines not on this page · raw message
t/t3903-stash.sh +72 -0
76 lines not on this page · raw message
t/t3905-stash-include-untracked.sh +26 -0
@@ -185,4 +185,30 @@ test_expect_success 'stash save --all is stash poppable' ' test -s .gitignore ' +test_expect_success 'stash push --include-untracked with pathspec' ' + >foo && + >bar && + git stash push --include-untracked -- foo && + test_path_is_file bar && + test_path_is_missing foo && + git stash pop && + test_path_is_file bar && + test_path_is_file foo +' + +test_expect_success 'stash push with $IFS character' ' + >"foo bar" && + >foo && + >bar && + git add foo* && + git stash push --include-untracked -- "foo b*" && + test_path_is_missing "foo bar" && + test_path_is_file foo && + test_path_is_file bar && + git stash pop && + test_path_is_file "foo bar" && + test_path_is_file foo && + test_path_is_file bar +' + test_done
Signature · 1 line
2.11.0.301.g86e6ecc671.dirty
PATCH v4 6/7 stash: use stash_push for no verb form
In reply to Thomas GummererNow that we have stash_push, which accepts pathspec arguments, use it instead of stash_save in git stash without any additional verbs.
This does introduce a small regression. Previously we allowed git stash -- -message, with a hyphen in front of the message. However git stash -- message without the hyphen was not allowed. After this change adding a message to the stash, with or without hyphen is no longer allowed.
While this now allows specifying a message with the -m flag, it also disallows messages without a hyphen. This is to prevent user errors, where a user tries to stash something with a message, but changes their mind, and now would like to apply a stash, but forgets to remove the -m flag. E.g. git stash -m mes^H^H^Happly would result in a stash with the message apply, while the user might have intended to apply a previous stash.
---
If this kind of regression introduced here is not acceptable, I think we could hide this change between some kind of config option, and transition users over later after a warning period.
Documentation/git-stash.txt | 8 ++++---- git-stash.sh | 16 ++++++++-------- t/t3903-stash.sh | 4 +--- 3 files changed, 13 insertions(+), 15 deletions(-)
Documentation/git-stash.txt +4 -4
@@ -13,11 +13,11 @@ SYNOPSIS 'git stash' drop [-q|--quiet] [<stash>] 'git stash' ( pop | apply ) [--index] [-q|--quiet] [<stash>] 'git stash' branch <branchname> [<stash>] -'git stash' [save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] - [-u|--include-untracked] [-a|--all] [<message>]] -'git stash' push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] +'git stash' save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [<message>] +'git stash' [push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] [-u|--include-untracked] [-a|--all] [-m|--message <message>]] - [--] [<pathspec>...] + [--] [<pathspec>...]] 'git stash' clear 'git stash' create [<message>] 'git stash' create [-m <message>] [-u|--include-untracked <untracked|all>]
git-stash.sh +8 -8
@@ -7,11 +7,11 @@ USAGE="list [<options>] or: $dashless drop [-q|--quiet] [<stash>] or: $dashless ( pop | apply ) [--index] [-q|--quiet] [<stash>] or: $dashless branch <branchname> [<stash>] - or: $dashless [save [--patch] [-k|--[no-]keep-index] [-q|--quiet] - [-u|--include-untracked] [-a|--all] [<message>]] - or: $dashless push [--patch] [-k|--[no-]keep-index] [-q|--quiet] - [-u|--include-untracked] [-a|--all] [-m <message>] - [-- <pathspec>...] + or: $dashless save [--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [<message>] + or: $dashless [push [--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [-m <message>] + [-- <pathspec>...]] or: $dashless clear" SUBDIRECTORY_OK=Yes
@@ -699,7 +699,7 @@ apply_to_branch () { } PARSE_CACHE='--not-parsed' -# The default command is "save" if nothing but options are given +# The default command is "push" if nothing but options are given seen_non_option= for opt do
@@ -709,7 +709,7 @@ do esac done -test -n "$seen_non_option" || set "save" "$@" +test -n "$seen_non_option" || set "push" "$@" # Main command set case "$1" in
@@ -760,7 +760,7 @@ branch) *) case $# in 0) - save_stash && + push_stash && say "$(gettext "(To restore them type \"git stash apply\")")" ;; *)
t/t3903-stash.sh +1 -3
@@ -274,9 +274,7 @@ test_expect_success 'stash --invalid-option' ' git add file2 && test_must_fail git stash --invalid-option && test_must_fail git stash save --invalid-option && - test bar5,bar6 = $(cat file),$(cat file2) && - git stash -- -message-starting-with-dash && - test bar,bar2 = $(cat file),$(cat file2) + test bar5,bar6 = $(cat file),$(cat file2) ' test_expect_success 'stash an added file' '
Signature · 1 line
2.11.0.301.g86e6ecc671.dirty
PATCH v4 7/7 stash: allow pathspecs in the no verb form
In reply to Thomas GummererNow that stash_push is used in the no verb form of stash, allow specifying the command line for this form as well. Always use -- to disambiguate pathspecs from other non-option arguments.
--- git-stash.sh | 1 + t/t3903-stash.sh | 15 +++++++++++++++ 2 files changed, 16 insertions(+)
git-stash.sh +1 -0
@@ -704,6 +704,7 @@ seen_non_option= for opt do case "$opt" in + --) break ;; -*) ;; *) seen_non_option=t; break ;; esac
t/t3903-stash.sh +15 -0
@@ -881,4 +881,19 @@ test_expect_success 'untracked files are left in place when -u is not given' ' test_path_is_file untracked ' +test_expect_success 'stash without verb with pathspec' ' + >"foo bar" && + >foo && + >bar && + git add foo* && + git stash -- "foo b*" && + test_path_is_missing "foo bar" && + test_path_is_file foo && + test_path_is_file bar && + git stash pop && + test_path_is_file "foo bar" && + test_path_is_file foo && + test_path_is_file bar +' + test_done
Signature · 1 line
2.11.0.301.g86e6ecc671.dirty
Quoted 2 lines · Thomas Gummerer
Thanks Peff and Junio for the review of the last round.
Sorry it seems like I messed up the In-Reply-To header. Previous rounds were at:
v1: http://public-inbox.org/git/[email protected]/
v2: http://public-inbox.org/git/[email protected]/
v3: http://public-inbox.org/git/[email protected]/
v5 cover stash: support pathspec argument
In reply to Thomas GummererThanks Matthieu, Peff and Junio for the discussion on v3 and v4.
Changes since v4:
Dropped patch 1 from the series, as it's already in master
Instead of changing the external interface to git stash create, only refactor the internal create_stash() function to take -m and -u arguments. This also simplifies the internal option parsing.
Make git stash -p an alias for git stash push -p, so git stash -p <pathspec> is allowed.
Interdiff below:
Documentation/git-stash.txt +2 -3
@@ -53,9 +53,8 @@ OPTIONS save [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [<message>]:: push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [-m|--message <message>] [--] [<pathspec>...]:: - Save your local modifications to a new 'stash' and roll them - back to HEAD (in the working tree and in the index). - The <message> part is optional and gives + Save your local modifications to a new 'stash', and run `git reset + --hard` to revert them. The <message> part is optional and gives the description along with the stashed state. For quickly making a snapshot, you can omit _both_ "save" and <message>, but giving only <message> does not trigger this action to prevent a misspelled
git-stash.sh +5 -34
@@ -67,51 +67,20 @@ create_stash () { case "$1" in -m|--message) shift - test -z ${1+x} && usage - stash_msg="$1" - new_style=t + stash_msg=${1-"BUG: create_stash () -m requires an argument"} ;; -u|--include-untracked) shift - test -z ${1+x} && usage - untracked="$1" - new_style=t + untracked=${1-"BUG: create_stash () -u requires an argument"} ;; --) shift - new_style=t - break - ;; - *) - if test -n "$new_style" - then - echo "invalid argument" - option="$1" - # TRANSLATORS: $option is an invalid option, like - # `--blah-blah'. The 7 spaces at the beginning of the - # second line correspond to "error: ". So you should line - # up the second line with however many characters the - # translation of "error: " takes in your language. E.g. in - # English this is: - # - # $ git stash save --blah-blah 2>&1 | head -n 2 - # error: unknown option for 'stash save': --blah-blah - # To provide a message, use git stash save -- '--blah-blah' - eval_gettextln "error: unknown option for 'stash create': \$option" - usage - fi break ;; esac shift done - if test -z "$new_style" - then - stash_msg="$*" - set -- - fi - git update-index -q --refresh if no_changes "$@" then
@@ -698,6 +667,8 @@ apply_to_branch () { } } +test "$1" = "-p" && set "push" "$@" + PARSE_CACHE='--not-parsed' # The default command is "push" if nothing but options are given seen_non_option=
@@ -740,7 +711,7 @@ clear) ;; create) shift - create_stash "$@" && echo "$w_commit" + create_stash -m "$*" && echo "$w_commit" ;; store) shift
t/t3903-stash.sh +0 -9
@@ -800,15 +800,6 @@ test_expect_success 'create with multiple arguments for the message' ' test_cmp expect actual ' -test_expect_success 'new style stash create stores correct message' ' - >foo && - git add foo && - STASH_ID=$(git stash create -m "create test message new style") && - echo "On master: create test message new style" >expect && - git show --pretty=%s -s ${STASH_ID} >actual && - test_cmp expect actual -' - test_expect_success 'stash -- <filename> stashes and restores the file' ' >foo && >bar &&
Thomas Gummerer (6):
stash: introduce push verb
stash: add test for the create command line arguments
stash: refactor stash_create
stash: teach 'push' (and 'create_stash') to honor pathspec
stash: use stash_push for no verb form
stash: allow pathspecs in the no verb form
Documentation/git-stash.txt | 16 ++++- git-stash.sh | 128 ++++++++++++++++++++++++++++++------- t/t3903-stash.sh | 118 +++++++++++++++++++++++++++++++++- t/t3905-stash-include-untracked.sh | 26 ++++++++ 4 files changed, 261 insertions(+), 27 deletions(-)
Signature · 1 line
2.11.0.301.g27b9849079.dirty
PATCH v5 1/6 stash: introduce push verb
Introduce a new git stash push verb in addition to git stash save. The push verb is used to transition from the current command line arguments to a more conventional way, in which the message is given as an argument to the -m option.
This allows us to have pathspecs at the end of the command line arguments like other Git commands do, so that the user can say which subset of paths to stash (and leave others behind).
--- git-stash.sh | 46 +++++++++++++++++++++++++++++++++++++++++++--- t/t3903-stash.sh | 9 +++++++++ 2 files changed, 52 insertions(+), 3 deletions(-)
git-stash.sh +43 -3
@@ -9,6 +9,8 @@ USAGE="list [<options>] or: $dashless branch <branchname> [<stash>] or: $dashless [save [--patch] [-k|--[no-]keep-index] [-q|--quiet] [-u|--include-untracked] [-a|--all] [<message>]] + or: $dashless push [--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [-m <message>] or: $dashless clear" SUBDIRECTORY_OK=Yes
@@ -189,10 +191,11 @@ store_stash () { return $ret } -save_stash () { +push_stash () { keep_index= patch_mode= untracked= + stash_msg= while test $# != 0 do case "$1" in
@@ -216,6 +219,11 @@ save_stash () { -a|--all) untracked=all ;; + -m|--message) + shift + test -z ${1+x} && usage + stash_msg=$1 + ;; --help) show_help ;;
@@ -251,8 +259,6 @@ save_stash () { die "$(gettext "Can't use --patch and --include-untracked or --all at the same time")" fi - stash_msg="$*" - git update-index -q --refresh if no_changes then
@@ -291,6 +297,36 @@ save_stash () { fi } +save_stash () { + push_options= + while test $# != 0 + do + case "$1" in + --) + shift + break + ;; + -*) + # pass all options through to push_stash + push_options="$push_options $1" + ;; + *) + break + ;; + esac + shift + done + + stash_msg="$*" + + if test -z "$stash_msg" + then + push_stash $push_options + else + push_stash $push_options -m "$stash_msg" + fi +} + have_stash () { git rev-parse --verify --quiet $ref_stash >/dev/null }
@@ -617,6 +653,10 @@ save) shift save_stash "$@" ;; +push) + shift + push_stash "$@" + ;; apply) shift apply_stash "$@"
t/t3903-stash.sh +9 -0
@@ -775,4 +775,13 @@ test_expect_success 'stash is not confused by partial renames' ' test_path_is_missing file ' +test_expect_success 'push -m shows right message' ' + >foo && + git add foo && + git stash push -m "test message" && + echo "stash@{0}: On master: test message" >expect && + git stash list -1 >actual && + test_cmp expect actual +' + test_done
Signature · 1 line
2.11.0.301.g27b9849079.dirty
PATCH v5 2/6 stash: add test for the create command line arguments
In reply to Thomas GummererCurrently there is no test showing the expected behaviour of git stash create's command line arguments. Add a test for that to show the current expected behaviour and to make sure future refactorings don't break those expectations.
--- t/t3903-stash.sh | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+)
t/t3903-stash.sh +18 -0
@@ -784,4 +784,22 @@ test_expect_success 'push -m shows right message' ' test_cmp expect actual ' +test_expect_success 'create stores correct message' ' + >foo && + git add foo && + STASH_ID=$(git stash create "create test message") && + echo "On master: create test message" >expect && + git show --pretty=%s -s ${STASH_ID} >actual && + test_cmp expect actual +' + +test_expect_success 'create with multiple arguments for the message' ' + >foo && + git add foo && + STASH_ID=$(git stash create test untracked) && + echo "On master: test untracked" >expect && + git show --pretty=%s -s ${STASH_ID} >actual && + test_cmp expect actual +' + test_done
Signature · 1 line
2.11.0.301.g27b9849079.dirty
PATCH v5 3/6 stash: refactor stash_create
In reply to Thomas GummererRefactor the internal stash_create function to use a -m flag for specifying the message and -u flag to indicate whether untracked files should be added to the stash.
This makes it easier to pass a pathspec argument to stash_create in the next patch.
The user interface for git stash create stays the same.
--- Documentation/git-stash.txt | 1 + git-stash.sh | 23 +++++++++++++++++++---- 2 files changed, 20 insertions(+), 4 deletions(-)
Documentation/git-stash.txt +1 -0
@@ -17,6 +17,7 @@ SYNOPSIS [-u|--include-untracked] [-a|--all] [<message>]] 'git stash' clear 'git stash' create [<message>] +'git stash' create [-m <message>] [-u|--include-untracked <untracked|all>] 'git stash' store [-m|--message <message>] [-q|--quiet] <commit> DESCRIPTION
git-stash.sh +19 -4
@@ -58,8 +58,23 @@ clear_stash () { } create_stash () { - stash_msg="$1" - untracked="$2" + stash_msg= + untracked= + new_style= + while test $# != 0 + do + case "$1" in + -m|--message) + shift + stash_msg=${1-"BUG: create_stash () -m requires an argument"} + ;; + -u|--include-untracked) + shift + untracked=${1-"BUG: create_stash () -u requires an argument"} + ;; + esac + shift + done git update-index -q --refresh if no_changes
@@ -268,7 +283,7 @@ push_stash () { git reflog exists $ref_stash || clear_stash || die "$(gettext "Cannot initialize stash")" - create_stash "$stash_msg" $untracked + create_stash -m "$stash_msg" -u "$untracked" store_stash -m "$stash_msg" -q $w_commit || die "$(gettext "Cannot save the current status")" say "$(eval_gettext "Saved working directory and index state \$stash_msg")"
@@ -667,7 +682,7 @@ clear) ;; create) shift - create_stash "$*" && echo "$w_commit" + create_stash -m "$*" && echo "$w_commit" ;; store) shift
Signature · 1 line
2.11.0.301.g27b9849079.dirty
Re: [PATCH v5 3/6] stash: refactor stash_create
Quoted 8 lines · Thomas Gummerer
Refactor the internal
stash_createfunction to use a -m flag for specifying the message and -u flag to indicate whether untracked files should be added to the stash.This makes it easier to pass a pathspec argument to
stash_createin the next patch.The user interface for git stash create stays the same.
Sounds good, but...
Documentation/git-stash.txt SYNOPSIS · line 21
Quoted 10 lines
Documentation/git-stash.txt +1
-0@@ -17,6 +17,7 @@ SYNOPSIS [-u|--include-untracked] [-a|--all] [<message>]] 'git stash' clear 'git stash' create [<message>] +'git stash' create [-m <message>] [-u|--include-untracked <untracked|all>] 'git stash' store [-m|--message <message>] [-q|--quiet] <commit>
Should this hunk be dropped from the manpage, then?
I think there is a similar one in the next patch that adds the "pathspec" argument, and should be dropped, too.
-Peff
Re: [PATCH v5 3/6] stash: refactor stash_create
Quoted 26 lines · Jeff King
Quoted 8 lines · Thomas Gummerer
Refactor the internal
stash_createfunction to use a -m flag for specifying the message and -u flag to indicate whether untracked files should be added to the stash.This makes it easier to pass a pathspec argument to
stash_createin the next patch.The user interface for git stash create stays the same.
Sounds good, but...
Documentation/git-stash.txt SYNOPSIS · line 21
Quoted 10 lines
Documentation/git-stash.txt +1
-0@@ -17,6 +17,7 @@ SYNOPSIS [-u|--include-untracked] [-a|--all] [<message>]] 'git stash' clear 'git stash' create [<message>] +'git stash' create [-m <message>] [-u|--include-untracked <untracked|all>] 'git stash' store [-m|--message <message>] [-q|--quiet] <commit>Should this hunk be dropped from the manpage, then?
Quoted 2 lines
I think there is a similar one in the next patch that adds the "pathspec" argument, and should be dropped, too.
Argh yes I should have been more careful. Thanks for catching.
Quoted 1 line
-Peff
PATCH v5 4/6 stash: teach 'push' (and 'create_stash') to honor pathspec
In reply to Thomas GummererWhile working on a repository, it's often helpful to stash the changes of a single or multiple files, and leave others alone. Unfortunately git currently offers no such option. git stash -p can be used to work around this, but it's often impractical when there are a lot of changes over multiple files.
Allow 'git stash push' to take pathspec to specify which paths to stash.
--- Documentation/git-stash.txt | 11 ++++++ git-stash.sh | 48 +++++++++++++++++++------ t/t3903-stash.sh | 72 ++++++++++++++++++++++++++++++++++++++ t/t3905-stash-include-untracked.sh | 26 ++++++++++++++ 4 files changed, 146 insertions(+), 11 deletions(-)
Documentation/git-stash.txt +11 -0
@@ -15,9 +15,13 @@ SYNOPSIS 'git stash' branch <branchname> [<stash>] 'git stash' [save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] [-u|--include-untracked] [-a|--all] [<message>]] +'git stash' push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [-m|--message <message>]] + [--] [<pathspec>...] 'git stash' clear 'git stash' create [<message>] 'git stash' create [-m <message>] [-u|--include-untracked <untracked|all>] + [-- <pathspec>...] 'git stash' store [-m|--message <message>] [-q|--quiet] <commit> DESCRIPTION
@@ -47,6 +51,7 @@ OPTIONS ------- save [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [<message>]:: +push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [-m|--message <message>] [--] [<pathspec>...]:: Save your local modifications to a new 'stash', and run `git reset --hard` to revert them. The <message> part is optional and gives
@@ -55,6 +60,12 @@ save [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q only <message> does not trigger this action to prevent a misspelled subcommand from making an unwanted stash. + +When pathspec is given to 'git stash push', the new stash records the +modified states only for the files that match the pathspec. The index +entries and working tree files are then rolled back to the state in +HEAD only for these files, too, leaving files that do not match the +pathspec intact. ++ If the `--keep-index` option is used, all changes already added to the index are left intact. +
git-stash.sh +37 -11
116 lines not on this page · raw message
t/t3903-stash.sh +72 -0
76 lines not on this page · raw message
t/t3905-stash-include-untracked.sh +26 -0
@@ -185,4 +185,30 @@ test_expect_success 'stash save --all is stash poppable' ' test -s .gitignore ' +test_expect_success 'stash push --include-untracked with pathspec' ' + >foo && + >bar && + git stash push --include-untracked -- foo && + test_path_is_file bar && + test_path_is_missing foo && + git stash pop && + test_path_is_file bar && + test_path_is_file foo +' + +test_expect_success 'stash push with $IFS character' ' + >"foo bar" && + >foo && + >bar && + git add foo* && + git stash push --include-untracked -- "foo b*" && + test_path_is_missing "foo bar" && + test_path_is_file foo && + test_path_is_file bar && + git stash pop && + test_path_is_file "foo bar" && + test_path_is_file foo && + test_path_is_file bar +' + test_done
Signature · 1 line
2.11.0.301.g27b9849079.dirty
PATCH v5 5/6 stash: use stash_push for no verb form
In reply to Thomas GummererNow that we have stash_push, which accepts pathspec arguments, use it instead of stash_save in git stash without any additional verbs.
Previously we allowed git stash -- -message, which is no longer allowed after this patch. Messages starting with a hyphen was allowed since 3c2eb80f, ("stash: simplify defaulting to "save" and reject unknown options"). However it was never the intent to allow that, but rather it was allowed accidentally.
--- Documentation/git-stash.txt | 8 ++++---- git-stash.sh | 16 ++++++++-------- t/t3903-stash.sh | 4 +--- 3 files changed, 13 insertions(+), 15 deletions(-)
Documentation/git-stash.txt +4 -4
@@ -13,11 +13,11 @@ SYNOPSIS 'git stash' drop [-q|--quiet] [<stash>] 'git stash' ( pop | apply ) [--index] [-q|--quiet] [<stash>] 'git stash' branch <branchname> [<stash>] -'git stash' [save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] - [-u|--include-untracked] [-a|--all] [<message>]] -'git stash' push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] +'git stash' save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [<message>] +'git stash' [push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] [-u|--include-untracked] [-a|--all] [-m|--message <message>]] - [--] [<pathspec>...] + [--] [<pathspec>...]] 'git stash' clear 'git stash' create [<message>] 'git stash' create [-m <message>] [-u|--include-untracked <untracked|all>]
git-stash.sh +8 -8
@@ -7,11 +7,11 @@ USAGE="list [<options>] or: $dashless drop [-q|--quiet] [<stash>] or: $dashless ( pop | apply ) [--index] [-q|--quiet] [<stash>] or: $dashless branch <branchname> [<stash>] - or: $dashless [save [--patch] [-k|--[no-]keep-index] [-q|--quiet] - [-u|--include-untracked] [-a|--all] [<message>]] - or: $dashless push [--patch] [-k|--[no-]keep-index] [-q|--quiet] - [-u|--include-untracked] [-a|--all] [-m <message>] - [-- <pathspec>...] + or: $dashless save [--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [<message>] + or: $dashless [push [--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [-m <message>] + [-- <pathspec>...]] or: $dashless clear" SUBDIRECTORY_OK=Yes
@@ -668,7 +668,7 @@ apply_to_branch () { } PARSE_CACHE='--not-parsed' -# The default command is "save" if nothing but options are given +# The default command is "push" if nothing but options are given seen_non_option= for opt do
@@ -678,7 +678,7 @@ do esac done -test -n "$seen_non_option" || set "save" "$@" +test -n "$seen_non_option" || set "push" "$@" # Main command set case "$1" in
@@ -729,7 +729,7 @@ branch) *) case $# in 0) - save_stash && + push_stash && say "$(gettext "(To restore them type \"git stash apply\")")" ;; *)
t/t3903-stash.sh +1 -3
@@ -274,9 +274,7 @@ test_expect_success 'stash --invalid-option' ' git add file2 && test_must_fail git stash --invalid-option && test_must_fail git stash save --invalid-option && - test bar5,bar6 = $(cat file),$(cat file2) && - git stash -- -message-starting-with-dash && - test bar,bar2 = $(cat file),$(cat file2) + test bar5,bar6 = $(cat file),$(cat file2) ' test_expect_success 'stash an added file' '
Signature · 1 line
2.11.0.301.g27b9849079.dirty
PATCH v5 6/6 stash: allow pathspecs in the no verb form
In reply to Thomas GummererNow that stash_push is used in the no verb form of stash, allow specifying the command line for this form as well. Always use -- to disambiguate pathspecs from other non-option arguments.
Also make git stash -p an alias for git stash push -p. This allows users to use git stash -p <pathspec>.
--- git-stash.sh | 3 +++ t/t3903-stash.sh | 15 +++++++++++++++ 2 files changed, 18 insertions(+)
git-stash.sh +3 -0
@@ -667,12 +667,15 @@ apply_to_branch () { } } +test "$1" = "-p" && set "push" "$@" + PARSE_CACHE='--not-parsed' # The default command is "push" if nothing but options are given seen_non_option= for opt do case "$opt" in + --) break ;; -*) ;; *) seen_non_option=t; break ;; esac
t/t3903-stash.sh +15 -0
@@ -872,4 +872,19 @@ test_expect_success 'untracked files are left in place when -u is not given' ' test_path_is_file untracked ' +test_expect_success 'stash without verb with pathspec' ' + >"foo bar" && + >foo && + >bar && + git add foo* && + git stash -- "foo b*" && + test_path_is_missing "foo bar" && + test_path_is_file foo && + test_path_is_file bar && + git stash pop && + test_path_is_file "foo bar" && + test_path_is_file foo && + test_path_is_file bar +' + test_done
Signature · 1 line
2.11.0.301.g27b9849079.dirty
Re: [PATCH v5 6/6] stash: allow pathspecs in the no verb form
Quoted 3 lines · Thomas Gummerer
Now that
stash_pushis used in the no verb form of stash, allow specifying the command line for this form as well. Always use -- to disambiguate pathspecs from other non-option arguments.
I think that makes sense.
Quoted 2 lines
Also make git stash -p an alias for git stash push -p. This allows users to use git stash -p <pathspec>.
And I think of all the options we discussed for handling "-p", I think this one makes the most sense.
It may be worth calling out in the documentation that this is how it works though, so people do not think that:
git stash -k -p <path>
would work ("git stash -k -p" _does_ happen to work due to the old options-only rule, but I think we should advertise the general form as "-p is an alias for "push -p").
-Peff
Re: [PATCH v5 6/6] stash: allow pathspecs in the no verb form
Quoted 14 lines · Jeff King
Quoted 3 lines · Thomas Gummerer
Now that
stash_pushis used in the no verb form of stash, allow specifying the command line for this form as well. Always use -- to disambiguate pathspecs from other non-option arguments.I think that makes sense.
Quoted 2 lines
Also make git stash -p an alias for git stash push -p. This allows users to use git stash -p <pathspec>.
And I think of all the options we discussed for handling "-p", I think this one makes the most sense.
Quoted 8 lines
It may be worth calling out in the documentation that this is how it works though, so people do not think that:
git stash -k -p <path>
would work ("git stash -k -p" _does_ happen to work due to the old options-only rule, but I think we should advertise the general form as "-p is an alias for "push -p").
Yeah, I think adding something about this in the documentation would be good. I'll add a paragraph about this in the re-roll.
Quoted 1 line
-Peff
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 43 lines · Junio C Hamano
Quoted 8 lines · Thomas Gummerer
Thanks Matthieu, Peff and Junio for the discussion on v3 and v4.
Changes since v4:
Dropped patch 1 from the series, as it's already in masterInstead of changing the external interface to git stash create, only refactor the internal
create_stash()function to take -m and -u arguments. This also simplifies the internal option parsing.Yay.
Quoted 2 lines
Make git stash -p an alias for git stash push -p, so git stash -p <pathspec> is allowed.
Nice.
Quoted 25 lines
Interdiff below:
Documentation/git-stash.txt +2
-3@@ -53,9 +53,8 @@ OPTIONS save [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [<message>]:: push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [-m|--message <message>] [--] [<pathspec>...]:: - Save your local modifications to a new 'stash' and roll them - back to HEAD (in the working tree and in the index). - The <message> part is optional and gives + Save your local modifications to a new 'stash', and run `git reset + --hard` to revert them. The <message> part is optional and gives the description along with the stashed state. For quickly making a snapshot, you can omit _both_ "save" and <message>, but giving only <message> does not trigger this action to prevent a misspelledgit-stash.sh +0
-0@@ -67,51 +67,20 @@ create_stash () { case "$1" in
Quoted 8 lines
git-stash.sh create_stash () { · line 70
Quoted 6 lines
git-stash.sh +1
-3-m|--message) shift - test -z ${1+x} && usage - stash_msg="$1" - new_style=t + stash_msg=${1-"BUG: create_stash () -m requires an argument"}Hmph, did you mean ${1?"BUG: ..."}? The same for the one in "-u".
Ah yes sorry, you're right course. Thanks.
Thomas Gummerer <[email protected]> writes:
[some people may see this message twice, as I forgot to check if the copy I received had "Some A . Body" not enclosed in dq; blindly doing "Reply-All" ended up listing an invalid address on my Cc: line and dropped by vger. apologies]
git-stash.sh create_stash () { · line 71
Quoted 13 lines
git-stash.sh +1
-3@@ -67,51 +67,20 @@ create_stash () { case "$1" in -m|--message) shift - test -z ${1+x} && usage - stash_msg="$1" - new_style=t + stash_msg=${1-"BUG: create_stash () -m requires an argument"} ;;
Did you mean ${1?"BUG: ..."} here and also "-u" below?
git-stash.sh create_stash () { · line 75
Quoted 7 lines
git-stash.sh +1
-3-u|--include-untracked) shift - test -z ${1+x} && usage - untracked="$1" - new_style=t + untracked=${1-"BUG: create_stash () -u requires an argument"} ;;
Other than that the whole series looked sensible to me.
Thanks, will replace but that may not happen today.
Quoted 7 lines · Junio C Hamano
Thomas Gummerer <[email protected]> writes:
[some people may see this message twice, as I forgot to check if the copy I received had "Some A . Body" not enclosed in dq; blindly doing "Reply-All" ended up listing an invalid address on my Cc: line and dropped by vger. apologies]
Quoted 15 lines
git-stash.sh create_stash () { · line 71
Quoted 13 lines
git-stash.sh +1
-3@@ -67,51 +67,20 @@ create_stash () { case "$1" in -m|--message) shift - test -z ${1+x} && usage - stash_msg="$1" - new_style=t + stash_msg=${1-"BUG: create_stash () -m requires an argument"} ;;Did you mean ${1?"BUG: ..."} here and also "-u" below?
Yeah, shell scripts are still confusing me sometimes. Thanks for catching. Would you mind fixing this up while queuing or do you want me to resend?
Quoted 11 lines
git-stash.sh create_stash () { · line 75
Quoted 7 lines
git-stash.sh +1
-3-u|--include-untracked) shift - test -z ${1+x} && usage - untracked="$1" - new_style=t + untracked=${1-"BUG: create_stash () -u requires an argument"} ;;Other than that the whole series looked sensible to me.
Thanks, will replace but that may not happen today.
Thanks!
Quoted 24 lines · Thomas Gummerer
Quoted 7 lines · Junio C Hamano
Thomas Gummerer <[email protected]> writes:
[some people may see this message twice, as I forgot to check if the copy I received had "Some A . Body" not enclosed in dq; blindly doing "Reply-All" ended up listing an invalid address on my Cc: line and dropped by vger. apologies]
Quoted 15 lines
git-stash.sh create_stash () { · line 71
Quoted 13 lines
git-stash.sh +1
-3@@ -67,51 +67,20 @@ create_stash () { case "$1" in -m|--message) shift - test -z ${1+x} && usage - stash_msg="$1" - new_style=t + stash_msg=${1-"BUG: create_stash () -m requires an argument"} ;;Did you mean ${1?"BUG: ..."} here and also "-u" below?
Quoted 3 lines
Yeah, shell scripts are still confusing me sometimes. Thanks for catching. Would you mind fixing this up while queuing or do you want me to resend?
I'll fix it up myself (please remind me if you notice that I forgot ;-).
v6 cover stash: support pathspec argument
In reply to Thomas GummererThanks Junio and Peff for comments on the last round.
Changes since then:
- removed mention of the "new form" of git stash create from the Documentation.
- Changed documentation for git stash without a verb, mentioning stash -p now being an alias for git stash push -p and that -- can be used as disambiguation for for pathspecs
- Fixed ${1-...} which should have been ${1?...}
- Removed unused new_style variable from create_stash, which was a leftover from perious rounds.
Interdiff below:
Documentation/git-stash.txt +7 -6
@@ -20,8 +20,6 @@ SYNOPSIS [--] [<pathspec>...]] 'git stash' clear 'git stash' create [<message>] -'git stash' create [-m <message>] [-u|--include-untracked <untracked|all>] - [-- <pathspec>...] 'git stash' store [-m|--message <message>] [-q|--quiet] <commit> DESCRIPTION
@@ -55,10 +53,13 @@ push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q Save your local modifications to a new 'stash', and run `git reset --hard` to revert them. The <message> part is optional and gives - the description along with the stashed state. For quickly making - a snapshot, you can omit _both_ "save" and <message>, but giving - only <message> does not trigger this action to prevent a misspelled - subcommand from making an unwanted stash. + the description along with the stashed state. ++ +For quickly making a snapshot, you can omit "push". In this mode, +non-option arguments are not allowed to prevent a misspelled +subcommand from making an unwanted stash. The two exceptions to this +are `stash -p` which acts as alias for `stash push -p` and pathspecs, +which are allowed after a double hyphen `--` for disambiguation. + When pathspec is given to 'git stash push', the new stash records the modified states only for the files that match the pathspec. The index
git-stash.sh +2 -3
@@ -61,17 +61,16 @@ clear_stash () { create_stash () { stash_msg= untracked= - new_style= while test $# != 0 do case "$1" in -m|--message) shift - stash_msg=${1-"BUG: create_stash () -m requires an argument"} + stash_msg=${1?"BUG: create_stash () -m requires an argument"} ;; -u|--include-untracked) shift - untracked=${1-"BUG: create_stash () -u requires an argument"} + untracked=${1?"BUG: create_stash () -u requires an argument"} ;; --) shift
Thomas Gummerer (6):
stash: introduce push verb
stash: add test for the create command line arguments
stash: refactor stash_create
stash: teach 'push' (and 'create_stash') to honor pathspec
stash: use stash_push for no verb form
stash: allow pathspecs in the no verb form
Documentation/git-stash.txt | 27 ++++++-- git-stash.sh | 127 ++++++++++++++++++++++++++++++------- t/t3903-stash.sh | 118 +++++++++++++++++++++++++++++++++- t/t3905-stash-include-untracked.sh | 26 ++++++++ 4 files changed, 267 insertions(+), 31 deletions(-)
Signature · 1 line
2.12.0.rc2.399.g0ca89a282
PATCH v6 1/6 stash: introduce push verb
Introduce a new git stash push verb in addition to git stash save. The push verb is used to transition from the current command line arguments to a more conventional way, in which the message is given as an argument to the -m option.
This allows us to have pathspecs at the end of the command line arguments like other Git commands do, so that the user can say which subset of paths to stash (and leave others behind).
--- Documentation/git-stash.txt | 3 +++ git-stash.sh | 46 ++++++++++++++++++++++++++++++++++++++++++--- t/t3903-stash.sh | 9 +++++++++ 3 files changed, 55 insertions(+), 3 deletions(-)
Documentation/git-stash.txt +3 -0
@@ -15,6 +15,8 @@ SYNOPSIS 'git stash' branch <branchname> [<stash>] 'git stash' [save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] [-u|--include-untracked] [-a|--all] [<message>]] +'git stash' push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [-m|--message <message>]] 'git stash' clear 'git stash' create [<message>] 'git stash' store [-m|--message <message>] [-q|--quiet] <commit>
@@ -46,6 +48,7 @@ OPTIONS ------- save [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [<message>]:: +push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [-m|--message <message>]:: Save your local modifications to a new 'stash', and run `git reset --hard` to revert them. The <message> part is optional and gives
git-stash.sh +43 -3
85 lines not on this page · raw message
t/t3903-stash.sh +9 -0
@@ -775,4 +775,13 @@ test_expect_success 'stash is not confused by partial renames' ' test_path_is_missing file ' +test_expect_success 'push -m shows right message' ' + >foo && + git add foo && + git stash push -m "test message" && + echo "stash@{0}: On master: test message" >expect && + git stash list -1 >actual && + test_cmp expect actual +' + test_done
Signature · 1 line
2.12.0.rc2.399.g0ca89a282
PATCH v6 2/6 stash: add test for the create command line arguments
In reply to Thomas GummererCurrently there is no test showing the expected behaviour of git stash create's command line arguments. Add a test for that to show the current expected behaviour and to make sure future refactorings don't break those expectations.
--- t/t3903-stash.sh | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+)
t/t3903-stash.sh +18 -0
@@ -784,4 +784,22 @@ test_expect_success 'push -m shows right message' ' test_cmp expect actual ' +test_expect_success 'create stores correct message' ' + >foo && + git add foo && + STASH_ID=$(git stash create "create test message") && + echo "On master: create test message" >expect && + git show --pretty=%s -s ${STASH_ID} >actual && + test_cmp expect actual +' + +test_expect_success 'create with multiple arguments for the message' ' + >foo && + git add foo && + STASH_ID=$(git stash create test untracked) && + echo "On master: test untracked" >expect && + git show --pretty=%s -s ${STASH_ID} >actual && + test_cmp expect actual +' + test_done
Signature · 1 line
2.12.0.rc2.399.g0ca89a282
PATCH v6 3/6 stash: refactor stash_create
In reply to Thomas GummererRefactor the internal stash_create function to use a -m flag for specifying the message and -u flag to indicate whether untracked files should be added to the stash.
This makes it easier to pass a pathspec argument to stash_create in the next patch.
The user interface for git stash create stays the same.
--- git-stash.sh | 22 ++++++++++++++++++---- 1 file changed, 18 insertions(+), 4 deletions(-)
git-stash.sh +18 -4
@@ -58,8 +58,22 @@ clear_stash () { } create_stash () { - stash_msg="$1" - untracked="$2" + stash_msg= + untracked= + while test $# != 0 + do + case "$1" in + -m|--message) + shift + stash_msg=${1?"BUG: create_stash () -m requires an argument"} + ;; + -u|--include-untracked) + shift + untracked=${1?"BUG: create_stash () -u requires an argument"} + ;; + esac + shift + done git update-index -q --refresh if no_changes
@@ -268,7 +282,7 @@ push_stash () { git reflog exists $ref_stash || clear_stash || die "$(gettext "Cannot initialize stash")" - create_stash "$stash_msg" $untracked + create_stash -m "$stash_msg" -u "$untracked" store_stash -m "$stash_msg" -q $w_commit || die "$(gettext "Cannot save the current status")" say "$(eval_gettext "Saved working directory and index state \$stash_msg")"
@@ -667,7 +681,7 @@ clear) ;; create) shift - create_stash "$*" && echo "$w_commit" + create_stash -m "$*" && echo "$w_commit" ;; store) shift
Signature · 1 line
2.12.0.rc2.399.g0ca89a282
PATCH v6 4/6 stash: teach 'push' (and 'create_stash') to honor pathspec
In reply to Thomas GummererWhile working on a repository, it's often helpful to stash the changes of a single or multiple files, and leave others alone. Unfortunately git currently offers no such option. git stash -p can be used to work around this, but it's often impractical when there are a lot of changes over multiple files.
Allow 'git stash push' to take pathspec to specify which paths to stash.
--- Documentation/git-stash.txt | 9 ++++- git-stash.sh | 48 +++++++++++++++++++------ t/t3903-stash.sh | 72 ++++++++++++++++++++++++++++++++++++++ t/t3905-stash-include-untracked.sh | 26 ++++++++++++++ 4 files changed, 143 insertions(+), 12 deletions(-)
Documentation/git-stash.txt +8 -1
@@ -17,6 +17,7 @@ SYNOPSIS [-u|--include-untracked] [-a|--all] [<message>]] 'git stash' push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] [-u|--include-untracked] [-a|--all] [-m|--message <message>]] + [--] [<pathspec>...] 'git stash' clear 'git stash' create [<message>] 'git stash' store [-m|--message <message>] [-q|--quiet] <commit>
@@ -48,7 +49,7 @@ OPTIONS ------- save [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [<message>]:: -push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [-m|--message <message>]:: +push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [-m|--message <message>] [--] [<pathspec>...]:: Save your local modifications to a new 'stash', and run `git reset --hard` to revert them. The <message> part is optional and gives
@@ -57,6 +58,12 @@ push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q only <message> does not trigger this action to prevent a misspelled subcommand from making an unwanted stash. + +When pathspec is given to 'git stash push', the new stash records the +modified states only for the files that match the pathspec. The index +entries and working tree files are then rolled back to the state in +HEAD only for these files, too, leaving files that do not match the +pathspec intact. ++ If the `--keep-index` option is used, all changes already added to the index are left intact. +
git-stash.sh +37 -11
116 lines not on this page · raw message
t/t3903-stash.sh +72 -0
76 lines not on this page · raw message
t/t3905-stash-include-untracked.sh +26 -0
@@ -185,4 +185,30 @@ test_expect_success 'stash save --all is stash poppable' ' test -s .gitignore ' +test_expect_success 'stash push --include-untracked with pathspec' ' + >foo && + >bar && + git stash push --include-untracked -- foo && + test_path_is_file bar && + test_path_is_missing foo && + git stash pop && + test_path_is_file bar && + test_path_is_file foo +' + +test_expect_success 'stash push with $IFS character' ' + >"foo bar" && + >foo && + >bar && + git add foo* && + git stash push --include-untracked -- "foo b*" && + test_path_is_missing "foo bar" && + test_path_is_file foo && + test_path_is_file bar && + git stash pop && + test_path_is_file "foo bar" && + test_path_is_file foo && + test_path_is_file bar +' + test_done
Signature · 1 line
2.12.0.rc2.399.g0ca89a282
Re: [PATCH v6 4/6] stash: teach 'push' (and 'create_stash') to honor pathspec
git-stash.sh push_stash () { · line 292
Quoted 1 line · Thomas Gummerer
git-stash.sh +0
-1- git reset --hard ${GIT_QUIET:+-q}
This hunk is probably the most important one to review in the whole series, in the sense that these are entirely new code that didn't exist in the original.
git-stash.sh push_stash () { · line 300
Quoted 4 lines
git-stash.sh +4
-0+ if test $# != 0 + then + saved_untracked= + if test -n "$(git ls-files --others -- "$@")"
I notice that "ls-files -o" used in the code before this series are almost always used with --exclude-standard but we do not set up the standard exclude pattern here. Is there a good reason to use (or not to use) it here as well?
git-stash.sh push_stash () { · line 305
Quoted 5 lines
git-stash.sh +5
-0+ then + saved_untracked=$( + git ls-files -z --others -- "$@" | + xargs -0 git stash create -u all --) + fi
Running the same ls-files twice look somewhat wasteful.
I suspect that we avoid "xargs -0" in our code from portability concern (isn't it a GNU invention?)
git-stash.sh push_stash () { · line 306
Quoted 1 line
git-stash.sh +1
-0+ git ls-files -z -- "$@" | xargs -0 git reset ${GIT_QUIET:+-q} --
Hmm, am I being naive to suspect that the above is a roundabout way to say:
git reset ${GIT_QUIET:+-q} -- "$@"or is an effect quite different from that intended here?
git-stash.sh push_stash () { · line 307
Quoted 1 line
git-stash.sh +1
-0+ git ls-files -z --modified -- "$@" | xargs -0 git checkout ${GIT_QUIET:+-q} HEAD --
Likewise. Wouldn't the above be equivalent to:
git checkout ${GIT_QUIET:+-q} HEAD -- "$@"Or is this trying to preserve paths modified in the working tree and fully added to the index?
git-stash.sh push_stash () { · line 310
Quoted 3 lines
git-stash.sh +3
-0+ if test -n "$(git ls-files -z --others -- "$@")" + then + git ls-files -z --others -- "$@" | xargs -0 git clean --force -d ${GIT_QUIET:+-q} --
Likewise. "ls-files --others" being the major part of what "clean" is about, I suspect the "ls-files piped to clean" is redundant. Do you even need a test? IOW, doesn't "git clean" with a pathspec that does not match anything silently succeed without doing anything harmful?
git-stash.sh push_stash () { · line 314
Quoted 4 lines
git-stash.sh +4
-0+ fi + if test -n "$saved_untracked" + then + git stash pop -q $saved_untracked
I see this thing was "created", and the whole point of "create" is to be different from "save/push" that automatically adds the result to the stash reflog. Should we be "pop"ing it, or did you mean to just call apply_stash on it?
Quoted 4 lines
git-stash.sh +4
-0+ fi + else + git reset --hard ${GIT_QUIET:+-q} + fi
Re: [PATCH v6 4/6] stash: teach 'push' (and 'create_stash') to honor pathspec
Quoted 8 lines · Junio C Hamano
git-stash.sh push_stash () { · line 292
Quoted 1 line · Thomas Gummerer
git-stash.sh +0
-1- git reset --hard ${GIT_QUIET:+-q}This hunk is probably the most important one to review in the whole series, in the sense that these are entirely new code that didn't exist in the original.
Quoted 9 lines
git-stash.sh push_stash () { · line 300
Quoted 4 lines
git-stash.sh +4
-0+ if test $# != 0 + then + saved_untracked= + if test -n "$(git ls-files --others -- "$@")"I notice that "ls-files -o" used in the code before this series are almost always used with --exclude-standard but we do not set up the standard exclude pattern here. Is there a good reason to use (or not to use) it here as well?
We probably should use it, not adding it was an oversight.
Quoted 20 lines
git-stash.sh push_stash () { · line 305
Quoted 5 lines
git-stash.sh +5
-0+ then + saved_untracked=$( + git ls-files -z --others -- "$@" | + xargs -0 git stash create -u all --) + fiRunning the same ls-files twice look somewhat wasteful.
I suspect that we avoid "xargs -0" in our code from portability concern (isn't it a GNU invention?)
git-stash.sh push_stash () { · line 306
Quoted 1 line
git-stash.sh +1
-0+ git ls-files -z -- "$@" | xargs -0 git reset ${GIT_QUIET:+-q} --Hmm, am I being naive to suspect that the above is a roundabout way to say:
git reset ${GIT_QUIET:+-q} -- "$@"or is an effect quite different from that intended here?
Quoted 8 lines
git-stash.sh push_stash () { · line 307
Quoted 1 line
git-stash.sh +1
-0+ git ls-files -z --modified -- "$@" | xargs -0 git checkout ${GIT_QUIET:+-q} HEAD --Likewise. Wouldn't the above be equivalent to:
git checkout ${GIT_QUIET:+-q} HEAD -- "$@"Or is this trying to preserve paths modified in the working tree and fully added to the index?.
No, it's not trying to do that (all the paths we're touching here would have been "reset" earlier, so it wouldn't change anything. However what this code tried to do is to allow "stash push -- path pathspec-not-in-repo", where "pathspec-not-in-repo" would end up tripping up "checkout" which does not accept pathspecs that are not in the index.
I think we should disallow such pathspecs in stash as well, except in the --include-untracked case, where it still makes sense.
This means we can't get rid of the "ls-files --modified" here, but we can in all other places, and get rid of the "stash_create" "stash_apply" dance to store the untracked files, simplifying this part quite a bit.
Will re-roll.
Quoted 26 lines
git-stash.sh push_stash () { · line 310
Quoted 4 lines
git-stash.sh +3
-0+ if test -n "$(git ls-files -z --others -- "$@")" + then + git ls-files -z --others -- "$@" | xargs -0 git clean --force -d ${GIT_QUIET:+-q} --Likewise. "ls-files --others" being the major part of what "clean" is about, I suspect the "ls-files piped to clean" is redundant. Do you even need a test? IOW, doesn't "git clean" with a pathspec that does not match anything silently succeed without doing anything harmful?
git-stash.sh push_stash () { · line 314
Quoted 4 lines
git-stash.sh +4
-0+ fi + if test -n "$saved_untracked" + then + git stash pop -q $saved_untrackedI see this thing was "created", and the whole point of "create" is to be different from "save/push" that automatically adds the result to the stash reflog. Should we be "pop"ing it, or did you mean to just call
apply_stashon it?Quoted 4 lines
git-stash.sh +4
-0+ fi + else + git reset --hard ${GIT_QUIET:+-q} + fi
PATCH v6 5/6 stash: use stash_push for no verb form
In reply to Thomas GummererNow that we have stash_push, which accepts pathspec arguments, use it instead of stash_save in git stash without any additional verbs.
Previously we allowed git stash -- -message, which is no longer allowed after this patch. Messages starting with a hyphen was allowed since 3c2eb80f, ("stash: simplify defaulting to "save" and reject unknown options"). However it was never the intent to allow that, but rather it was allowed accidentally.
--- Documentation/git-stash.txt | 8 ++++---- git-stash.sh | 16 ++++++++-------- t/t3903-stash.sh | 4 +--- 3 files changed, 13 insertions(+), 15 deletions(-)
Documentation/git-stash.txt +4 -4
@@ -13,11 +13,11 @@ SYNOPSIS 'git stash' drop [-q|--quiet] [<stash>] 'git stash' ( pop | apply ) [--index] [-q|--quiet] [<stash>] 'git stash' branch <branchname> [<stash>] -'git stash' [save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] - [-u|--include-untracked] [-a|--all] [<message>]] -'git stash' push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] +'git stash' save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [<message>] +'git stash' [push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] [-u|--include-untracked] [-a|--all] [-m|--message <message>]] - [--] [<pathspec>...] + [--] [<pathspec>...]] 'git stash' clear 'git stash' create [<message>] 'git stash' store [-m|--message <message>] [-q|--quiet] <commit>
git-stash.sh +8 -8
@@ -7,11 +7,11 @@ USAGE="list [<options>] or: $dashless drop [-q|--quiet] [<stash>] or: $dashless ( pop | apply ) [--index] [-q|--quiet] [<stash>] or: $dashless branch <branchname> [<stash>] - or: $dashless [save [--patch] [-k|--[no-]keep-index] [-q|--quiet] - [-u|--include-untracked] [-a|--all] [<message>]] - or: $dashless push [--patch] [-k|--[no-]keep-index] [-q|--quiet] - [-u|--include-untracked] [-a|--all] [-m <message>] - [-- <pathspec>...] + or: $dashless save [--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [<message>] + or: $dashless [push [--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [-m <message>] + [-- <pathspec>...]] or: $dashless clear" SUBDIRECTORY_OK=Yes
@@ -667,7 +667,7 @@ apply_to_branch () { } PARSE_CACHE='--not-parsed' -# The default command is "save" if nothing but options are given +# The default command is "push" if nothing but options are given seen_non_option= for opt do
@@ -677,7 +677,7 @@ do esac done -test -n "$seen_non_option" || set "save" "$@" +test -n "$seen_non_option" || set "push" "$@" # Main command set case "$1" in
@@ -728,7 +728,7 @@ branch) *) case $# in 0) - save_stash && + push_stash && say "$(gettext "(To restore them type \"git stash apply\")")" ;; *)
t/t3903-stash.sh +1 -3
@@ -274,9 +274,7 @@ test_expect_success 'stash --invalid-option' ' git add file2 && test_must_fail git stash --invalid-option && test_must_fail git stash save --invalid-option && - test bar5,bar6 = $(cat file),$(cat file2) && - git stash -- -message-starting-with-dash && - test bar,bar2 = $(cat file),$(cat file2) + test bar5,bar6 = $(cat file),$(cat file2) ' test_expect_success 'stash an added file' '
Signature · 1 line
2.12.0.rc2.399.g0ca89a282
PATCH v6 6/6 stash: allow pathspecs in the no verb form
In reply to Thomas GummererNow that stash_push is used in the no verb form of stash, allow specifying the command line for this form as well. Always use -- to disambiguate pathspecs from other non-option arguments.
Also make git stash -p an alias for git stash push -p. This allows users to use git stash -p <pathspec>.
--- Documentation/git-stash.txt | 11 +++++++---- git-stash.sh | 3 +++ t/t3903-stash.sh | 15 +++++++++++++++ 3 files changed, 25 insertions(+), 4 deletions(-)
Documentation/git-stash.txt +7 -4
@@ -53,10 +53,13 @@ push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q Save your local modifications to a new 'stash', and run `git reset --hard` to revert them. The <message> part is optional and gives - the description along with the stashed state. For quickly making - a snapshot, you can omit _both_ "save" and <message>, but giving - only <message> does not trigger this action to prevent a misspelled - subcommand from making an unwanted stash. + the description along with the stashed state. ++ +For quickly making a snapshot, you can omit "push". In this mode, +non-option arguments are not allowed to prevent a misspelled +subcommand from making an unwanted stash. The two exceptions to this +are `stash -p` which acts as alias for `stash push -p` and pathspecs, +which are allowed after a double hyphen `--` for disambiguation. + When pathspec is given to 'git stash push', the new stash records the modified states only for the files that match the pathspec. The index
git-stash.sh +3 -0
@@ -666,12 +666,15 @@ apply_to_branch () { } } +test "$1" = "-p" && set "push" "$@" + PARSE_CACHE='--not-parsed' # The default command is "push" if nothing but options are given seen_non_option= for opt do case "$opt" in + --) break ;; -*) ;; *) seen_non_option=t; break ;; esac
t/t3903-stash.sh +15 -0
@@ -872,4 +872,19 @@ test_expect_success 'untracked files are left in place when -u is not given' ' test_path_is_file untracked ' +test_expect_success 'stash without verb with pathspec' ' + >"foo bar" && + >foo && + >bar && + git add foo* && + git stash -- "foo b*" && + test_path_is_missing "foo bar" && + test_path_is_file foo && + test_path_is_file bar && + git stash pop && + test_path_is_file "foo bar" && + test_path_is_file foo && + test_path_is_file bar +' + test_done
Signature · 1 line
2.12.0.rc2.399.g0ca89a282
Quoted 4 lines · Thomas Gummerer
Thanks Junio and Peff for comments on the last round.
Changes since then:
Quoted 8 lines
- removed mention of the "new form" of git stash create from the Documentation.
- Changed documentation for git stash without a verb, mentioning stash -p now being an alias for git stash push -p and that -- can be used as disambiguation for for pathspecs
- Fixed ${1-...} which should have been ${1?...}
- Removed unusednew_stylevariable fromcreate_stash, which was a leftover from perious rounds.
I gave it one more read-through, and didn't see anything objectionable. Thanks for seeing this through!
-Peff
Documentation/git-stash.txt push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q · line 55
Quoted 4 lines · Thomas Gummerer
Documentation/git-stash.txt +0
-0@@ -55,10 +53,13 @@ push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q Save your local modifications to a new 'stash', and run `git reset --hard` to revert them. The <message> part is optional and gives
I didn't notice this during v5 review, but the above seems to be based on the codebase before your documentation update (which used to be part of the series in older iteration). I had to tweak the series to apply on top of your 20a7e06172 ("Documentation/stash:
remove mention of git reset --hard", 2017-02-12) while queuing, so please double check the result when it is pushed out to 'pu'.
Thanks.
Documentation/git-stash.txt push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q · line 55
Quoted 4 lines · Thomas Gummerer
Documentation/git-stash.txt +0
-0@@ -55,10 +53,13 @@ push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q Save your local modifications to a new 'stash', and run `git reset --hard` to revert them. The <message> part is optional and gives
I didn't notice this during v5 review, but the above seems to be based on the codebase before your documentation update (which used to be part of the series in older iteration). I had to tweak the series to apply on top of your 20a7e06172 ("Documentation/stash:
remove mention of git reset --hard", 2017-02-12) while queuing, so please double check the result when it is pushed out to 'pu'.
Thanks.
Quoted 4 lines · Junio C Hamano
Quoted 2 lines · Thomas Gummerer
(quoted diff) +0
-0@@ -55,10 +53,13 @@ push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q
Quoted 9 lines
Documentation/git-stash.txt push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q · line 55
Quoted 2 lines
Documentation/git-stash.txt +0
-0Save your local modifications to a new 'stash', and run `git reset --hard` to revert them. The <message> part is optional and givesI didn't notice this during v5 review, but the above seems to be based on the codebase before your documentation update (which used to be part of the series in older iteration). I had to tweak the series to apply on top of your
20a7e06172("Documentation/stash:
remove mention of git reset --hard", 2017-02-12) while queuing, so please double check the result when it is pushed out to 'pu'.
Sorry about that. What you queued looks good to me, I will however send a re-roll based on your comments on 4/6. (And I'll make sure to base it on 20a7e06172)
v7 cover stash: support pathspec argument
In reply to Thomas GummererThanks Junio for more comments on the last round, and Peff for reading through it as well.
Changes since v6:
- If no --include-untracked option is given to git stash push, and a pathspec is not in the repository, error out instead of ignoring it. This brings it in line with things like checkout, and also allows us to simplify the code internally.
- Simplify the code for rolling back the changes from the working tree. This is enabled by the changes to the pathspec handling.
- There's no more "xargs -0", so there should be no more portability concerns.
- Adjust the tests and improve some of the titles a bit
Interdiff:
git-stash.sh +6 -17
@@ -278,12 +278,15 @@ push_stash () { die "$(gettext "Can't use --patch and --include-untracked or --all at the same time")" fi + test -n "$untracked" || git ls-files --error-unmatch -- "$@" >/dev/null || exit 1 + git update-index -q --refresh if no_changes "$@" then say "$(gettext "No local changes to save")" exit 0 fi + git reflog exists $ref_stash || clear_stash || die "$(gettext "Cannot initialize stash")"
@@ -296,23 +299,9 @@ push_stash () { then if test $# != 0 then - saved_untracked= - if test -n "$(git ls-files --others -- "$@")" - then - saved_untracked=$( - git ls-files -z --others -- "$@" | - xargs -0 git stash create -u all --) - fi - git ls-files -z -- "$@" | xargs -0 git reset ${GIT_QUIET:+-q} -- - git ls-files -z --modified -- "$@" | xargs -0 git checkout ${GIT_QUIET:+-q} HEAD -- - if test -n "$(git ls-files -z --others -- "$@")" - then - git ls-files -z --others -- "$@" | xargs -0 git clean --force -d ${GIT_QUIET:+-q} -- - fi - if test -n "$saved_untracked" - then - git stash pop -q $saved_untracked - fi + git reset ${GIT_QUIET:+-q} -- "$@" + git checkout ${GIT_QUIET:+-q} HEAD -- $(git ls-files -z --modified "$@") + git clean --force ${GIT_QUIET:+-q} -d -- "$@" else git reset --hard ${GIT_QUIET:+-q} fi
t/t3903-stash.sh +15 -11
@@ -800,7 +800,7 @@ test_expect_success 'create with multiple arguments for the message' ' test_cmp expect actual ' -test_expect_success 'stash -- <filename> stashes and restores the file' ' +test_expect_success 'stash -- <pathspec> stashes and restores the file' ' >foo && >bar && git add foo bar &&
@@ -812,7 +812,7 @@ test_expect_success 'stash -- <filename> stashes and restores the file' ' test_path_is_file bar ' -test_expect_success 'stash with multiple filename arguments' ' +test_expect_success 'stash with multiple pathspec arguments' ' >foo && >bar && >extra &&
@@ -842,25 +842,29 @@ test_expect_success 'stash with file including $IFS character' ' test_path_is_file bar ' -test_expect_success 'stash push -p with pathspec shows no changes only onece' ' - >file && - git add file && - git stash push -p not-file >actual && +test_expect_success 'stash push -p with pathspec shows no changes only once' ' + >foo && + git add foo && + git commit -m "tmp" && + git stash push -p foo >actual && echo "No local changes to save" >expect && + git reset --hard HEAD~ && test_cmp expect actual ' test_expect_success 'stash push with pathspec shows no changes when there are none' ' - >file && - git add file && - git stash push not-file >actual && + >foo && + git add foo && + git commit -m "tmp" && + git stash push foo >actual && echo "No local changes to save" >expect && + git reset --hard HEAD~ && test_cmp expect actual ' -test_expect_success 'untracked file is not removed when using pathspecs' ' +test_expect_success 'stash push with pathspec not in the repository errors out' ' >untracked && - git stash push untracked && + test_must_fail git stash push untracked && test_path_is_file untracked '
Thomas Gummerer (6):
stash: introduce push verb
stash: add test for the create command line arguments
stash: refactor stash_create
stash: teach 'push' (and 'create_stash') to honor pathspec
stash: use stash_push for no verb form
stash: allow pathspecs in the no verb form
Documentation/git-stash.txt | 25 ++++++-- git-stash.sh | 114 +++++++++++++++++++++++++++------- t/t3903-stash.sh | 122 ++++++++++++++++++++++++++++++++++++- t/t3905-stash-include-untracked.sh | 26 ++++++++ 4 files changed, 257 insertions(+), 30 deletions(-)
Signature · 1 line
2.11.0.301.g275aeb250c.dirty
PATCH v7 1/6 stash: introduce push verb
Introduce a new git stash push verb in addition to git stash save. The push verb is used to transition from the current command line arguments to a more conventional way, in which the message is given as an argument to the -m option.
This allows us to have pathspecs at the end of the command line arguments like other Git commands do, so that the user can say which subset of paths to stash (and leave others behind).
--- Documentation/git-stash.txt | 3 +++ git-stash.sh | 46 ++++++++++++++++++++++++++++++++++++++++++--- t/t3903-stash.sh | 9 +++++++++ 3 files changed, 55 insertions(+), 3 deletions(-)
Documentation/git-stash.txt +3 -0
@@ -15,6 +15,8 @@ SYNOPSIS 'git stash' branch <branchname> [<stash>] 'git stash' [save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] [-u|--include-untracked] [-a|--all] [<message>]] +'git stash' push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [-m|--message <message>]] 'git stash' clear 'git stash' create [<message>] 'git stash' store [-m|--message <message>] [-q|--quiet] <commit>
@@ -46,6 +48,7 @@ OPTIONS ------- save [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [<message>]:: +push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [-m|--message <message>]:: Save your local modifications to a new 'stash' and roll them back to HEAD (in the working tree and in the index).
git-stash.sh +43 -3
85 lines not on this page · raw message
t/t3903-stash.sh +9 -0
@@ -775,4 +775,13 @@ test_expect_success 'stash is not confused by partial renames' ' test_path_is_missing file ' +test_expect_success 'push -m shows right message' ' + >foo && + git add foo && + git stash push -m "test message" && + echo "stash@{0}: On master: test message" >expect && + git stash list -1 >actual && + test_cmp expect actual +' + test_done
Signature · 1 line
2.11.0.301.g275aeb250c.dirty
PATCH v7 2/6 stash: add test for the create command line arguments
In reply to Thomas GummererCurrently there is no test showing the expected behaviour of git stash create's command line arguments. Add a test for that to show the current expected behaviour and to make sure future refactorings don't break those expectations.
--- t/t3903-stash.sh | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+)
t/t3903-stash.sh +18 -0
@@ -784,4 +784,22 @@ test_expect_success 'push -m shows right message' ' test_cmp expect actual ' +test_expect_success 'create stores correct message' ' + >foo && + git add foo && + STASH_ID=$(git stash create "create test message") && + echo "On master: create test message" >expect && + git show --pretty=%s -s ${STASH_ID} >actual && + test_cmp expect actual +' + +test_expect_success 'create with multiple arguments for the message' ' + >foo && + git add foo && + STASH_ID=$(git stash create test untracked) && + echo "On master: test untracked" >expect && + git show --pretty=%s -s ${STASH_ID} >actual && + test_cmp expect actual +' + test_done
Signature · 1 line
2.11.0.301.g275aeb250c.dirty
PATCH v7 3/6 stash: refactor stash_create
In reply to Thomas GummererRefactor the internal stash_create function to use a -m flag for specifying the message and -u flag to indicate whether untracked files should be added to the stash.
This makes it easier to pass a pathspec argument to stash_create in the next patch.
The user interface for git stash create stays the same.
--- git-stash.sh | 22 ++++++++++++++++++---- 1 file changed, 18 insertions(+), 4 deletions(-)
git-stash.sh +18 -4
@@ -58,8 +58,22 @@ clear_stash () { } create_stash () { - stash_msg="$1" - untracked="$2" + stash_msg= + untracked= + while test $# != 0 + do + case "$1" in + -m|--message) + shift + stash_msg=${1?"BUG: create_stash () -m requires an argument"} + ;; + -u|--include-untracked) + shift + untracked=${1?"BUG: create_stash () -u requires an argument"} + ;; + esac + shift + done git update-index -q --refresh if no_changes
@@ -268,7 +282,7 @@ push_stash () { git reflog exists $ref_stash || clear_stash || die "$(gettext "Cannot initialize stash")" - create_stash "$stash_msg" $untracked + create_stash -m "$stash_msg" -u "$untracked" store_stash -m "$stash_msg" -q $w_commit || die "$(gettext "Cannot save the current status")" say "$(eval_gettext "Saved working directory and index state \$stash_msg")"
@@ -667,7 +681,7 @@ clear) ;; create) shift - create_stash "$*" && echo "$w_commit" + create_stash -m "$*" && echo "$w_commit" ;; store) shift
Signature · 1 line
2.11.0.301.g275aeb250c.dirty
PATCH v7 4/6 stash: teach 'push' (and 'create_stash') to honor pathspec
In reply to Thomas GummererWhile working on a repository, it's often helpful to stash the changes of a single or multiple files, and leave others alone. Unfortunately git currently offers no such option. git stash -p can be used to work around this, but it's often impractical when there are a lot of changes over multiple files.
Allow 'git stash push' to take pathspec to specify which paths to stash.
--- Documentation/git-stash.txt | 9 ++++- git-stash.sh | 37 +++++++++++++------ t/t3903-stash.sh | 76 ++++++++++++++++++++++++++++++++++++++ t/t3905-stash-include-untracked.sh | 26 +++++++++++++ 4 files changed, 136 insertions(+), 12 deletions(-)
Documentation/git-stash.txt +8 -1
@@ -17,6 +17,7 @@ SYNOPSIS [-u|--include-untracked] [-a|--all] [<message>]] 'git stash' push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] [-u|--include-untracked] [-a|--all] [-m|--message <message>]] + [--] [<pathspec>...] 'git stash' clear 'git stash' create [<message>] 'git stash' store [-m|--message <message>] [-q|--quiet] <commit>
@@ -48,7 +49,7 @@ OPTIONS ------- save [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [<message>]:: -push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [-m|--message <message>]:: +push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [-m|--message <message>] [--] [<pathspec>...]:: Save your local modifications to a new 'stash' and roll them back to HEAD (in the working tree and in the index).
@@ -58,6 +59,12 @@ push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q only <message> does not trigger this action to prevent a misspelled subcommand from making an unwanted stash. + +When pathspec is given to 'git stash push', the new stash records the +modified states only for the files that match the pathspec. The index +entries and working tree files are then rolled back to the state in +HEAD only for these files, too, leaving files that do not match the +pathspec intact. ++ If the `--keep-index` option is used, all changes already added to the index are left intact. +
git-stash.sh +26 -11
@@ -11,6 +11,7 @@ USAGE="list [<options>] [-u|--include-untracked] [-a|--all] [<message>]] or: $dashless push [--patch] [-k|--[no-]keep-index] [-q|--quiet] [-u|--include-untracked] [-a|--all] [-m <message>] + [-- <pathspec>...] or: $dashless clear" SUBDIRECTORY_OK=Yes
@@ -35,15 +36,15 @@ else fi no_changes () { - git diff-index --quiet --cached HEAD --ignore-submodules -- && - git diff-files --quiet --ignore-submodules && + git diff-index --quiet --cached HEAD --ignore-submodules -- "$@" && + git diff-files --quiet --ignore-submodules -- "$@" && (test -z "$untracked" || test -z "$(untracked_files)") } untracked_files () { excl_opt=--exclude-standard test "$untracked" = "all" && excl_opt= - git ls-files -o -z $excl_opt + git ls-files -o -z $excl_opt -- "$@" } clear_stash () {
@@ -71,12 +72,16 @@ create_stash () { shift untracked=${1?"BUG: create_stash () -u requires an argument"} ;; + --) + shift + break + ;; esac shift done git update-index -q --refresh - if no_changes + if no_changes "$@" then exit 0 fi
@@ -108,7 +113,7 @@ create_stash () { # Untracked files are stored by themselves in a parentless commit, for # ease of unpacking later. u_commit=$( - untracked_files | ( + untracked_files "$@" | ( GIT_INDEX_FILE="$TMPindex" && export GIT_INDEX_FILE && rm -f "$TMPindex" &&
@@ -131,7 +136,7 @@ create_stash () { git read-tree --index-output="$TMPindex" -m $i_tree && GIT_INDEX_FILE="$TMPindex" && export GIT_INDEX_FILE && - git diff-index --name-only -z HEAD -- >"$TMP-stagenames" && + git diff-index --name-only -z HEAD -- "$@" >"$TMP-stagenames" && git update-index -z --add --remove --stdin <"$TMP-stagenames" && git write-tree && rm -f "$TMPindex"
@@ -145,7 +150,7 @@ create_stash () { # find out what the user wants GIT_INDEX_FILE="$TMP-index" \ - git add--interactive --patch=stash -- && + git add--interactive --patch=stash -- "$@" && # state of the working tree w_tree=$(GIT_INDEX_FILE="$TMP-index" git write-tree) ||
@@ -273,27 +278,37 @@ push_stash () { die "$(gettext "Can't use --patch and --include-untracked or --all at the same time")" fi + test -n "$untracked" || git ls-files --error-unmatch -- "$@" >/dev/null || exit 1 + git update-index -q --refresh - if no_changes + if no_changes "$@" then say "$(gettext "No local changes to save")" exit 0 fi + git reflog exists $ref_stash || clear_stash || die "$(gettext "Cannot initialize stash")" - create_stash -m "$stash_msg" -u "$untracked" + create_stash -m "$stash_msg" -u "$untracked" -- "$@" store_stash -m "$stash_msg" -q $w_commit || die "$(gettext "Cannot save the current status")" say "$(eval_gettext "Saved working directory and index state \$stash_msg")" if test -z "$patch_mode" then - git reset --hard ${GIT_QUIET:+-q} + if test $# != 0 + then + git reset ${GIT_QUIET:+-q} -- "$@" + git checkout ${GIT_QUIET:+-q} HEAD -- $(git ls-files -z --modified "$@") + git clean --force ${GIT_QUIET:+-q} -d -- "$@" + else + git reset --hard ${GIT_QUIET:+-q} + fi test "$untracked" = "all" && CLEAN_X_OPTION=-x || CLEAN_X_OPTION= if test -n "$untracked" then - git clean --force --quiet -d $CLEAN_X_OPTION + git clean --force --quiet -d $CLEAN_X_OPTION -- "$@" fi if test "$keep_index" = "t" && test -n "$i_tree"
t/t3903-stash.sh +76 -0
80 lines not on this page · raw message
t/t3905-stash-include-untracked.sh +26 -0
@@ -185,4 +185,30 @@ test_expect_success 'stash save --all is stash poppable' ' test -s .gitignore ' +test_expect_success 'stash push --include-untracked with pathspec' ' + >foo && + >bar && + git stash push --include-untracked -- foo && + test_path_is_file bar && + test_path_is_missing foo && + git stash pop && + test_path_is_file bar && + test_path_is_file foo +' + +test_expect_success 'stash push with $IFS character' ' + >"foo bar" && + >foo && + >bar && + git add foo* && + git stash push --include-untracked -- "foo b*" && + test_path_is_missing "foo bar" && + test_path_is_file foo && + test_path_is_file bar && + git stash pop && + test_path_is_file "foo bar" && + test_path_is_file foo && + test_path_is_file bar +' + test_done
Signature · 1 line
2.11.0.301.g275aeb250c.dirty
Re: [PATCH v7 4/6] stash: teach 'push' (and 'create_stash') to honor pathspec
git-stash.sh push_stash () { · line 281
Quoted 1 line · Thomas Gummerer
git-stash.sh +1
-0+ test -n "$untracked" || git ls-files --error-unmatch -- "$@" >/dev/null || exit 1
This silent "exit 1" made me scratch my head, but --error-unmatch would have already given an error message, like
error: pathspec 'no such' did not match any file(s) known to git. Did you forget to 'git add'?
so that would be OK.
Re: [PATCH v7 4/6] stash: teach 'push' (and 'create_stash') to honor pathspec
Quoted 11 lines · Junio C Hamano
git-stash.sh push_stash () { · line 281
Quoted 1 line · Thomas Gummerer
git-stash.sh +1
-0+ test -n "$untracked" || git ls-files --error-unmatch -- "$@" >/dev/null || exit 1This silent "exit 1" made me scratch my head, but --error-unmatch would have already given an error message, like
error: pathspec 'no such' did not match any file(s) known to git. Did you forget to 'git add'?
so that would be OK.
Yeah exactly, the plan was to let --error-unmatch print the error message, as it's better at giving a good error message than we could easily do here I think.
Maybe this deserves a comment so others won't have the same doubts about this line?
Re: [PATCH v7 4/6] stash: teach 'push' (and 'create_stash') to honor pathspec
Quoted 11 lines · Thomas Gummerer
Quoted 10 lines · Junio C Hamano
git-stash.sh push_stash () { · line 281
Quoted 1 line · Thomas Gummerer
git-stash.sh +1
-0+ test -n "$untracked" || git ls-files --error-unmatch -- "$@" >/dev/null || exit 1This silent "exit 1" made me scratch my head, but --error-unmatch would have already given an error message, like
error: pathspec 'no such' did not match any file(s) known to git. Did you forget to 'git add'?
Quoted 8 lines
Quoted 1 line
so that would be OK.
Yeah exactly, the plan was to let --error-unmatch print the error message, as it's better at giving a good error message than we could easily do here I think.
Maybe this deserves a comment so others won't have the same doubts about this line?
Nah, I do not think so. It probably is obvious for those who write (and read) "--error-unmatch". I was just being slow to realize that the sole point of that option was to complain ;-)
Re: [PATCH v7 4/6] stash: teach 'push' (and 'create_stash') to honor pathspec
In reply to Thomas GummererReview
Quoted 7 lines · Thomas Gummerer
(quoted diff) +4
-1if test -z "$patch_mode" then - git reset --hard ${GIT_QUIET:+-q} + if test $# != 0 + then + git reset ${GIT_QUIET:+-q} -- "$@" + git checkout ${GIT_QUIET:+-q} HEAD -- $(git ls-files -z --modified "$@")
"ls-files -z" on the command line?
Apparently new tests do not cover the correctness of this codepath.
I wonder if this
git ls-files -z --modified "$@" | git checkout-index -z --force --stdin
is what the above "checkout" wanted to do. The "reset" in the previous step presumably updated the index entries that match specified pathspec to those of the HEAD, so checking out the paths that match "$@" from the index would be the same as checking them out from the HEAD (while updating the index with them).
Perhaps squash the following into an appropriate patch in the series?
git-stash.sh | 3 ++- t/t3903-stash.sh | 16 ++++++++++++++++ 2 files changed, 18 insertions(+), 1 deletion(-)
git-stash.sh +2 -1
@@ -300,7 +300,8 @@ push_stash () { if test $# != 0 then git reset ${GIT_QUIET:+-q} -- "$@" - git checkout ${GIT_QUIET:+-q} HEAD -- $(git ls-files -z --modified "$@") + git ls-files -z --modified -- "$@" | + git checkout-index -z --force --stdin git clean --force ${GIT_QUIET:+-q} -d -- "$@" else git reset --hard ${GIT_QUIET:+-q}
t/t3903-stash.sh +16 -0
@@ -891,4 +891,20 @@ test_expect_success 'stash without verb with pathspec' ' test_path_is_file bar ' +test_expect_success 'stash with pathspec matching multiple paths' ' + echo original >file && + echo original >other-file && + git commit -m "two" file other-file && + echo modified >file && + echo modified >other-file && + git stash -- "*file" && + echo original >expect && + test_cmp expect file && + test_cmp expect other-file && + git stash pop && + echo modified >expect && + test_cmp expect file && + test_cmp expect other-file +' + test_done
Re: [PATCH v7 4/6] stash: teach 'push' (and 'create_stash') to honor pathspec
Quoted 16 lines · Junio C Hamano
Review
Quoted 7 lines · Thomas Gummerer
(quoted diff) +4
-1if test -z "$patch_mode" then - git reset --hard ${GIT_QUIET:+-q} + if test $# != 0 + then + git reset ${GIT_QUIET:+-q} -- "$@" + git checkout ${GIT_QUIET:+-q} HEAD -- $(git ls-files -z --modified "$@")"ls-files -z" on the command line?
Apparently new tests do not cover the correctness of this codepath.
I wonder if this
Quoted 8 lines
git ls-files -z --modified "$@" | git checkout-index -z --force --stdinis what the above "checkout" wanted to do. The "reset" in the previous step presumably updated the index entries that match specified pathspec to those of the HEAD, so checking out the paths that match "$@" from the index would be the same as checking them out from the HEAD (while updating the index with them).
Yes, you're completely right, this is exactly what it should have done. Sorry for being slow on getting this right.
Quoted 2 lines
Perhaps squash the following into an appropriate patch in the series?
Thanks, I'll squash this in and re-roll.
Quoted 43 lines
git-stash.sh | 3 ++- t/t3903-stash.sh | 16 ++++++++++++++++ 2 files changed, 18 insertions(+), 1 deletion(-)git-stash.sh +2
-1@@ -300,7 +300,8 @@ push_stash () { if test $# != 0 then git reset ${GIT_QUIET:+-q} -- "$@" - git checkout ${GIT_QUIET:+-q} HEAD -- $(git ls-files -z --modified "$@") + git ls-files -z --modified -- "$@" | + git checkout-index -z --force --stdin git clean --force ${GIT_QUIET:+-q} -d -- "$@" else git reset --hard ${GIT_QUIET:+-q}t/t3903-stash.sh +16
-0@@ -891,4 +891,20 @@ test_expect_success 'stash without verb with pathspec' ' test_path_is_file bar ' +test_expect_success 'stash with pathspec matching multiple paths' ' + echo original >file && + echo original >other-file && + git commit -m "two" file other-file && + echo modified >file && + echo modified >other-file && + git stash -- "*file" && + echo original >expect && + test_cmp expect file && + test_cmp expect other-file && + git stash pop && + echo modified >expect && + test_cmp expect file && + test_cmp expect other-file +' + test_done
Re: [PATCH v7 4/6] stash: teach 'push' (and 'create_stash') to honor pathspec
In reply to Thomas Gummerergit-stash.sh push_stash () { · line 303
Quoted 7 lines · Thomas Gummerer
git-stash.sh +4
-1if test -z "$patch_mode" then - git reset --hard ${GIT_QUIET:+-q} + if test $# != 0 + then + git reset ${GIT_QUIET:+-q} -- "$@" + git checkout ${GIT_QUIET:+-q} HEAD -- $(git ls-files -z --modified "$@")
"ls-files -z" on the command line?
Apparently new tests do not cover the correctness of this codepath.
I wonder if this
git ls-files -z --modified "$@" | git checkout-index -z --stdin
is what the above "checkout" wanted to do. The "reset" in the previous step presumably updated the index entries that match specified pathspec to those of the HEAD, so checking out the paths that match "$@" from the index would be the same as checking them out from the HEAD (while updating the index with them).
git-stash.sh push_stash () { · line 307
Quoted 4 lines
git-stash.sh +4
-0+ git clean --force ${GIT_QUIET:+-q} -d -- "$@" + else + git reset --hard ${GIT_QUIET:+-q} + fi
Thanks.
PATCH v7 5/6 stash: use stash_push for no verb form
In reply to Thomas GummererNow that we have stash_push, which accepts pathspec arguments, use it instead of stash_save in git stash without any additional verbs.
Previously we allowed git stash -- -message, which is no longer allowed after this patch. Messages starting with a hyphen was allowed since 3c2eb80f, ("stash: simplify defaulting to "save" and reject unknown options"). However it was never the intent to allow that, but rather it was allowed accidentally.
--- Documentation/git-stash.txt | 8 ++++---- git-stash.sh | 16 ++++++++-------- t/t3903-stash.sh | 4 +--- 3 files changed, 13 insertions(+), 15 deletions(-)
Documentation/git-stash.txt +4 -4
@@ -13,11 +13,11 @@ SYNOPSIS 'git stash' drop [-q|--quiet] [<stash>] 'git stash' ( pop | apply ) [--index] [-q|--quiet] [<stash>] 'git stash' branch <branchname> [<stash>] -'git stash' [save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] - [-u|--include-untracked] [-a|--all] [<message>]] -'git stash' push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] +'git stash' save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [<message>] +'git stash' [push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] [-u|--include-untracked] [-a|--all] [-m|--message <message>]] - [--] [<pathspec>...] + [--] [<pathspec>...]] 'git stash' clear 'git stash' create [<message>] 'git stash' store [-m|--message <message>] [-q|--quiet] <commit>
git-stash.sh +8 -8
@@ -7,11 +7,11 @@ USAGE="list [<options>] or: $dashless drop [-q|--quiet] [<stash>] or: $dashless ( pop | apply ) [--index] [-q|--quiet] [<stash>] or: $dashless branch <branchname> [<stash>] - or: $dashless [save [--patch] [-k|--[no-]keep-index] [-q|--quiet] - [-u|--include-untracked] [-a|--all] [<message>]] - or: $dashless push [--patch] [-k|--[no-]keep-index] [-q|--quiet] - [-u|--include-untracked] [-a|--all] [-m <message>] - [-- <pathspec>...] + or: $dashless save [--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [<message>] + or: $dashless [push [--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [-m <message>] + [-- <pathspec>...]] or: $dashless clear" SUBDIRECTORY_OK=Yes
@@ -656,7 +656,7 @@ apply_to_branch () { } PARSE_CACHE='--not-parsed' -# The default command is "save" if nothing but options are given +# The default command is "push" if nothing but options are given seen_non_option= for opt do
@@ -666,7 +666,7 @@ do esac done -test -n "$seen_non_option" || set "save" "$@" +test -n "$seen_non_option" || set "push" "$@" # Main command set case "$1" in
@@ -717,7 +717,7 @@ branch) *) case $# in 0) - save_stash && + push_stash && say "$(gettext "(To restore them type \"git stash apply\")")" ;; *)
t/t3903-stash.sh +1 -3
@@ -274,9 +274,7 @@ test_expect_success 'stash --invalid-option' ' git add file2 && test_must_fail git stash --invalid-option && test_must_fail git stash save --invalid-option && - test bar5,bar6 = $(cat file),$(cat file2) && - git stash -- -message-starting-with-dash && - test bar,bar2 = $(cat file),$(cat file2) + test bar5,bar6 = $(cat file),$(cat file2) ' test_expect_success 'stash an added file' '
Signature · 1 line
2.11.0.301.g275aeb250c.dirty
PATCH v7 6/6 stash: allow pathspecs in the no verb form
In reply to Thomas GummererNow that stash_push is used in the no verb form of stash, allow specifying the command line for this form as well. Always use -- to disambiguate pathspecs from other non-option arguments.
Also make git stash -p an alias for git stash push -p. This allows users to use git stash -p <pathspec>.
--- Documentation/git-stash.txt | 11 +++++++---- git-stash.sh | 3 +++ t/t3903-stash.sh | 15 +++++++++++++++ 3 files changed, 25 insertions(+), 4 deletions(-)
Documentation/git-stash.txt +7 -4
@@ -54,10 +54,13 @@ push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q Save your local modifications to a new 'stash' and roll them back to HEAD (in the working tree and in the index). The <message> part is optional and gives - the description along with the stashed state. For quickly making - a snapshot, you can omit _both_ "save" and <message>, but giving - only <message> does not trigger this action to prevent a misspelled - subcommand from making an unwanted stash. + the description along with the stashed state. ++ +For quickly making a snapshot, you can omit "push". In this mode, +non-option arguments are not allowed to prevent a misspelled +subcommand from making an unwanted stash. The two exceptions to this +are `stash -p` which acts as alias for `stash push -p` and pathspecs, +which are allowed after a double hyphen `--` for disambiguation. + When pathspec is given to 'git stash push', the new stash records the modified states only for the files that match the pathspec. The index
git-stash.sh +3 -0
@@ -655,12 +655,15 @@ apply_to_branch () { } } +test "$1" = "-p" && set "push" "$@" + PARSE_CACHE='--not-parsed' # The default command is "push" if nothing but options are given seen_non_option= for opt do case "$opt" in + --) break ;; -*) ;; *) seen_non_option=t; break ;; esac
t/t3903-stash.sh +15 -0
@@ -876,4 +876,19 @@ test_expect_success 'untracked files are left in place when -u is not given' ' test_path_is_file untracked ' +test_expect_success 'stash without verb with pathspec' ' + >"foo bar" && + >foo && + >bar && + git add foo* && + git stash -- "foo b*" && + test_path_is_missing "foo bar" && + test_path_is_file foo && + test_path_is_file bar && + git stash pop && + test_path_is_file "foo bar" && + test_path_is_file foo && + test_path_is_file bar +' + test_done
Signature · 1 line
2.11.0.301.g275aeb250c.dirty
v8 cover stash: support pathspec argument
In reply to Thomas GummererThanks Junio for the review and the squashable diff with the fix for my errors.
I changed it a tiny bit, to use git stash push instead of git stash, so the complete diff could go into 4/6, where I think I think the test fits best.
Interdiff below:
git-stash.sh +2 -0
@@ -300,6 +300,8 @@ push_stash () { if test $# != 0 then git reset ${GIT_QUIET:+-q} -- "$@" + git ls-files -z --modified -- "$@" | + git checkout-index -z --force --stdin git checkout ${GIT_QUIET:+-q} HEAD -- $(git ls-files -z --modified "$@") git clean --force ${GIT_QUIET:+-q} -d -- "$@" else
t/t3903-stash.sh +16 -0
@@ -842,6 +842,22 @@ test_expect_success 'stash with file including $IFS character' ' test_path_is_file bar ' +test_expect_success 'stash with pathspec matching multiple paths' ' + echo original >file && + echo original >other-file && + git commit -m "two" file other-file && + echo modified >file && + echo modified >other-file && + git stash push -- "*file" && + echo original >expect && + test_cmp expect file && + test_cmp expect other-file && + git stash pop && + echo modified >expect && + test_cmp expect file && + test_cmp expect other-file +' + test_expect_success 'stash push -p with pathspec shows no changes only once' ' >foo && git add foo &&
Thomas Gummerer (6):
stash: introduce push verb
stash: add test for the create command line arguments
stash: refactor stash_create
stash: teach 'push' (and 'create_stash') to honor pathspec
stash: use stash_push for no verb form
stash: allow pathspecs in the no verb form
Documentation/git-stash.txt | 25 +++++-- git-stash.sh | 116 +++++++++++++++++++++++++------ t/t3903-stash.sh | 138 ++++++++++++++++++++++++++++++++++++- t/t3905-stash-include-untracked.sh | 26 +++++++ 4 files changed, 275 insertions(+), 30 deletions(-)
Signature · 1 line
2.12.0.428.g67fe103aa
PATCH v8 1/6 stash: introduce push verb
Introduce a new git stash push verb in addition to git stash save. The push verb is used to transition from the current command line arguments to a more conventional way, in which the message is given as an argument to the -m option.
This allows us to have pathspecs at the end of the command line arguments like other Git commands do, so that the user can say which subset of paths to stash (and leave others behind).
--- Documentation/git-stash.txt | 3 +++ git-stash.sh | 46 ++++++++++++++++++++++++++++++++++++++++++--- t/t3903-stash.sh | 9 +++++++++ 3 files changed, 55 insertions(+), 3 deletions(-)
Documentation/git-stash.txt +3 -0
@@ -15,6 +15,8 @@ SYNOPSIS 'git stash' branch <branchname> [<stash>] 'git stash' [save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] [-u|--include-untracked] [-a|--all] [<message>]] +'git stash' push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [-m|--message <message>]] 'git stash' clear 'git stash' create [<message>] 'git stash' store [-m|--message <message>] [-q|--quiet] <commit>
@@ -46,6 +48,7 @@ OPTIONS ------- save [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [<message>]:: +push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [-m|--message <message>]:: Save your local modifications to a new 'stash' and roll them back to HEAD (in the working tree and in the index).
git-stash.sh +43 -3
85 lines not on this page · raw message
t/t3903-stash.sh +9 -0
@@ -775,4 +775,13 @@ test_expect_success 'stash is not confused by partial renames' ' test_path_is_missing file ' +test_expect_success 'push -m shows right message' ' + >foo && + git add foo && + git stash push -m "test message" && + echo "stash@{0}: On master: test message" >expect && + git stash list -1 >actual && + test_cmp expect actual +' + test_done
Signature · 1 line
2.12.0.428.g67fe103aa
PATCH v8 2/6 stash: add test for the create command line arguments
In reply to Thomas GummererCurrently there is no test showing the expected behaviour of git stash create's command line arguments. Add a test for that to show the current expected behaviour and to make sure future refactorings don't break those expectations.
--- t/t3903-stash.sh | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+)
t/t3903-stash.sh +18 -0
@@ -784,4 +784,22 @@ test_expect_success 'push -m shows right message' ' test_cmp expect actual ' +test_expect_success 'create stores correct message' ' + >foo && + git add foo && + STASH_ID=$(git stash create "create test message") && + echo "On master: create test message" >expect && + git show --pretty=%s -s ${STASH_ID} >actual && + test_cmp expect actual +' + +test_expect_success 'create with multiple arguments for the message' ' + >foo && + git add foo && + STASH_ID=$(git stash create test untracked) && + echo "On master: test untracked" >expect && + git show --pretty=%s -s ${STASH_ID} >actual && + test_cmp expect actual +' + test_done
Signature · 1 line
2.12.0.428.g67fe103aa
PATCH v8 3/6 stash: refactor stash_create
In reply to Thomas GummererRefactor the internal stash_create function to use a -m flag for specifying the message and -u flag to indicate whether untracked files should be added to the stash.
This makes it easier to pass a pathspec argument to stash_create in the next patch.
The user interface for git stash create stays the same.
--- git-stash.sh | 22 ++++++++++++++++++---- 1 file changed, 18 insertions(+), 4 deletions(-)
git-stash.sh +18 -4
@@ -58,8 +58,22 @@ clear_stash () { } create_stash () { - stash_msg="$1" - untracked="$2" + stash_msg= + untracked= + while test $# != 0 + do + case "$1" in + -m|--message) + shift + stash_msg=${1?"BUG: create_stash () -m requires an argument"} + ;; + -u|--include-untracked) + shift + untracked=${1?"BUG: create_stash () -u requires an argument"} + ;; + esac + shift + done git update-index -q --refresh if no_changes
@@ -268,7 +282,7 @@ push_stash () { git reflog exists $ref_stash || clear_stash || die "$(gettext "Cannot initialize stash")" - create_stash "$stash_msg" $untracked + create_stash -m "$stash_msg" -u "$untracked" store_stash -m "$stash_msg" -q $w_commit || die "$(gettext "Cannot save the current status")" say "$(eval_gettext "Saved working directory and index state \$stash_msg")"
@@ -667,7 +681,7 @@ clear) ;; create) shift - create_stash "$*" && echo "$w_commit" + create_stash -m "$*" && echo "$w_commit" ;; store) shift
Signature · 1 line
2.12.0.428.g67fe103aa
PATCH v8 4/6 stash: teach 'push' (and 'create_stash') to honor pathspec
In reply to Thomas GummererWhile working on a repository, it's often helpful to stash the changes of a single or multiple files, and leave others alone. Unfortunately git currently offers no such option. git stash -p can be used to work around this, but it's often impractical when there are a lot of changes over multiple files.
Allow 'git stash push' to take pathspec to specify which paths to stash.
--- Documentation/git-stash.txt | 9 +++- git-stash.sh | 39 +++++++++++----- t/t3903-stash.sh | 92 ++++++++++++++++++++++++++++++++++++++ t/t3905-stash-include-untracked.sh | 26 +++++++++++ 4 files changed, 154 insertions(+), 12 deletions(-)
Documentation/git-stash.txt +8 -1
@@ -17,6 +17,7 @@ SYNOPSIS [-u|--include-untracked] [-a|--all] [<message>]] 'git stash' push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] [-u|--include-untracked] [-a|--all] [-m|--message <message>]] + [--] [<pathspec>...] 'git stash' clear 'git stash' create [<message>] 'git stash' store [-m|--message <message>] [-q|--quiet] <commit>
@@ -48,7 +49,7 @@ OPTIONS ------- save [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [<message>]:: -push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [-m|--message <message>]:: +push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [-m|--message <message>] [--] [<pathspec>...]:: Save your local modifications to a new 'stash' and roll them back to HEAD (in the working tree and in the index).
@@ -58,6 +59,12 @@ push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q only <message> does not trigger this action to prevent a misspelled subcommand from making an unwanted stash. + +When pathspec is given to 'git stash push', the new stash records the +modified states only for the files that match the pathspec. The index +entries and working tree files are then rolled back to the state in +HEAD only for these files, too, leaving files that do not match the +pathspec intact. ++ If the `--keep-index` option is used, all changes already added to the index are left intact. +
git-stash.sh +28 -11
@@ -11,6 +11,7 @@ USAGE="list [<options>] [-u|--include-untracked] [-a|--all] [<message>]] or: $dashless push [--patch] [-k|--[no-]keep-index] [-q|--quiet] [-u|--include-untracked] [-a|--all] [-m <message>] + [-- <pathspec>...] or: $dashless clear" SUBDIRECTORY_OK=Yes
@@ -35,15 +36,15 @@ else fi no_changes () { - git diff-index --quiet --cached HEAD --ignore-submodules -- && - git diff-files --quiet --ignore-submodules && + git diff-index --quiet --cached HEAD --ignore-submodules -- "$@" && + git diff-files --quiet --ignore-submodules -- "$@" && (test -z "$untracked" || test -z "$(untracked_files)") } untracked_files () { excl_opt=--exclude-standard test "$untracked" = "all" && excl_opt= - git ls-files -o -z $excl_opt + git ls-files -o -z $excl_opt -- "$@" } clear_stash () {
@@ -71,12 +72,16 @@ create_stash () { shift untracked=${1?"BUG: create_stash () -u requires an argument"} ;; + --) + shift + break + ;; esac shift done git update-index -q --refresh - if no_changes + if no_changes "$@" then exit 0 fi
@@ -108,7 +113,7 @@ create_stash () { # Untracked files are stored by themselves in a parentless commit, for # ease of unpacking later. u_commit=$( - untracked_files | ( + untracked_files "$@" | ( GIT_INDEX_FILE="$TMPindex" && export GIT_INDEX_FILE && rm -f "$TMPindex" &&
@@ -131,7 +136,7 @@ create_stash () { git read-tree --index-output="$TMPindex" -m $i_tree && GIT_INDEX_FILE="$TMPindex" && export GIT_INDEX_FILE && - git diff-index --name-only -z HEAD -- >"$TMP-stagenames" && + git diff-index --name-only -z HEAD -- "$@" >"$TMP-stagenames" && git update-index -z --add --remove --stdin <"$TMP-stagenames" && git write-tree && rm -f "$TMPindex"
@@ -145,7 +150,7 @@ create_stash () { # find out what the user wants GIT_INDEX_FILE="$TMP-index" \ - git add--interactive --patch=stash -- && + git add--interactive --patch=stash -- "$@" && # state of the working tree w_tree=$(GIT_INDEX_FILE="$TMP-index" git write-tree) ||
@@ -273,27 +278,39 @@ push_stash () { die "$(gettext "Can't use --patch and --include-untracked or --all at the same time")" fi + test -n "$untracked" || git ls-files --error-unmatch -- "$@" >/dev/null || exit 1 + git update-index -q --refresh - if no_changes + if no_changes "$@" then say "$(gettext "No local changes to save")" exit 0 fi + git reflog exists $ref_stash || clear_stash || die "$(gettext "Cannot initialize stash")" - create_stash -m "$stash_msg" -u "$untracked" + create_stash -m "$stash_msg" -u "$untracked" -- "$@" store_stash -m "$stash_msg" -q $w_commit || die "$(gettext "Cannot save the current status")" say "$(eval_gettext "Saved working directory and index state \$stash_msg")" if test -z "$patch_mode" then - git reset --hard ${GIT_QUIET:+-q} + if test $# != 0 + then + git reset ${GIT_QUIET:+-q} -- "$@" + git ls-files -z --modified -- "$@" | + git checkout-index -z --force --stdin + git checkout ${GIT_QUIET:+-q} HEAD -- $(git ls-files -z --modified "$@") + git clean --force ${GIT_QUIET:+-q} -d -- "$@" + else + git reset --hard ${GIT_QUIET:+-q} + fi test "$untracked" = "all" && CLEAN_X_OPTION=-x || CLEAN_X_OPTION= if test -n "$untracked" then - git clean --force --quiet -d $CLEAN_X_OPTION + git clean --force --quiet -d $CLEAN_X_OPTION -- "$@" fi if test "$keep_index" = "t" && test -n "$i_tree"
t/t3903-stash.sh +92 -0
96 lines not on this page · raw message
t/t3905-stash-include-untracked.sh +26 -0
@@ -185,4 +185,30 @@ test_expect_success 'stash save --all is stash poppable' ' test -s .gitignore ' +test_expect_success 'stash push --include-untracked with pathspec' ' + >foo && + >bar && + git stash push --include-untracked -- foo && + test_path_is_file bar && + test_path_is_missing foo && + git stash pop && + test_path_is_file bar && + test_path_is_file foo +' + +test_expect_success 'stash push with $IFS character' ' + >"foo bar" && + >foo && + >bar && + git add foo* && + git stash push --include-untracked -- "foo b*" && + test_path_is_missing "foo bar" && + test_path_is_file foo && + test_path_is_file bar && + git stash pop && + test_path_is_file "foo bar" && + test_path_is_file foo && + test_path_is_file bar +' + test_done
Signature · 1 line
2.12.0.428.g67fe103aa
Re: [PATCH v8 4/6] stash: teach 'push' (and 'create_stash') to honor pathspec
git-stash.sh push_stash () { · line 305
Quoted 4 lines · Thomas Gummerer
git-stash.sh +4
-0+ git reset ${GIT_QUIET:+-q} -- "$@" + git ls-files -z --modified -- "$@" | + git checkout-index -z --force --stdin + git checkout ${GIT_QUIET:+-q} HEAD -- $(git ls-files -z --modified "$@")
I think you forgot to remove this line, whose correction was added as two lines immediately before it. I'll remove it while queuing.
git-stash.sh push_stash () { · line 306
Quoted 1 line
git-stash.sh +1
-0+ git clean --force ${GIT_QUIET:+-q} -d -- "$@"
Thanks.
Re: [PATCH v8 4/6] stash: teach 'push' (and 'create_stash') to honor pathspec
Quoted 9 lines · Junio C Hamano
git-stash.sh push_stash () { · line 305
Quoted 4 lines · Thomas Gummerer
git-stash.sh +4
-0+ git reset ${GIT_QUIET:+-q} -- "$@" + git ls-files -z --modified -- "$@" | + git checkout-index -z --force --stdin + git checkout ${GIT_QUIET:+-q} HEAD -- $(git ls-files -z --modified "$@")I think you forgot to remove this line, whose correction was added as two lines immediately before it. I'll remove it while queuing.
Yes, sorry. What you queued looks good to me, thanks!
Quoted 3 lines
git-stash.sh push_stash () { · line 306
Quoted 1 line
git-stash.sh +1
-0+ git clean --force ${GIT_QUIET:+-q} -d -- "$@"Thanks.
Re: [PATCH v8 4/6] stash: teach 'push' (and 'create_stash') to honor pathspec
Quoted 11 lines · Thomas Gummerer
Quoted 9 lines · Junio C Hamano
git-stash.sh push_stash () { · line 305
Quoted 4 lines · Thomas Gummerer
git-stash.sh +4
-0+ git reset ${GIT_QUIET:+-q} -- "$@" + git ls-files -z --modified -- "$@" | + git checkout-index -z --force --stdin + git checkout ${GIT_QUIET:+-q} HEAD -- $(git ls-files -z --modified "$@")I think you forgot to remove this line, whose correction was added as two lines immediately before it. I'll remove it while queuing.
Quoted 1 line
Yes, sorry. What you queued looks good to me, thanks!
Thanks for double-checking, and thanks for working on the topic. I think this is ready for 'next'.
PATCH v8 5/6 stash: use stash_push for no verb form
In reply to Thomas GummererNow that we have stash_push, which accepts pathspec arguments, use it instead of stash_save in git stash without any additional verbs.
Previously we allowed git stash -- -message, which is no longer allowed after this patch. Messages starting with a hyphen was allowed since 3c2eb80f, ("stash: simplify defaulting to "save" and reject unknown options"). However it was never the intent to allow that, but rather it was allowed accidentally.
--- Documentation/git-stash.txt | 8 ++++---- git-stash.sh | 16 ++++++++-------- t/t3903-stash.sh | 4 +--- 3 files changed, 13 insertions(+), 15 deletions(-)
Documentation/git-stash.txt +4 -4
@@ -13,11 +13,11 @@ SYNOPSIS 'git stash' drop [-q|--quiet] [<stash>] 'git stash' ( pop | apply ) [--index] [-q|--quiet] [<stash>] 'git stash' branch <branchname> [<stash>] -'git stash' [save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] - [-u|--include-untracked] [-a|--all] [<message>]] -'git stash' push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] +'git stash' save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [<message>] +'git stash' [push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] [-u|--include-untracked] [-a|--all] [-m|--message <message>]] - [--] [<pathspec>...] + [--] [<pathspec>...]] 'git stash' clear 'git stash' create [<message>] 'git stash' store [-m|--message <message>] [-q|--quiet] <commit>
git-stash.sh +8 -8
@@ -7,11 +7,11 @@ USAGE="list [<options>] or: $dashless drop [-q|--quiet] [<stash>] or: $dashless ( pop | apply ) [--index] [-q|--quiet] [<stash>] or: $dashless branch <branchname> [<stash>] - or: $dashless [save [--patch] [-k|--[no-]keep-index] [-q|--quiet] - [-u|--include-untracked] [-a|--all] [<message>]] - or: $dashless push [--patch] [-k|--[no-]keep-index] [-q|--quiet] - [-u|--include-untracked] [-a|--all] [-m <message>] - [-- <pathspec>...] + or: $dashless save [--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [<message>] + or: $dashless [push [--patch] [-k|--[no-]keep-index] [-q|--quiet] + [-u|--include-untracked] [-a|--all] [-m <message>] + [-- <pathspec>...]] or: $dashless clear" SUBDIRECTORY_OK=Yes
@@ -658,7 +658,7 @@ apply_to_branch () { } PARSE_CACHE='--not-parsed' -# The default command is "save" if nothing but options are given +# The default command is "push" if nothing but options are given seen_non_option= for opt do
@@ -668,7 +668,7 @@ do esac done -test -n "$seen_non_option" || set "save" "$@" +test -n "$seen_non_option" || set "push" "$@" # Main command set case "$1" in
@@ -719,7 +719,7 @@ branch) *) case $# in 0) - save_stash && + push_stash && say "$(gettext "(To restore them type \"git stash apply\")")" ;; *)
t/t3903-stash.sh +1 -3
@@ -274,9 +274,7 @@ test_expect_success 'stash --invalid-option' ' git add file2 && test_must_fail git stash --invalid-option && test_must_fail git stash save --invalid-option && - test bar5,bar6 = $(cat file),$(cat file2) && - git stash -- -message-starting-with-dash && - test bar,bar2 = $(cat file),$(cat file2) + test bar5,bar6 = $(cat file),$(cat file2) ' test_expect_success 'stash an added file' '
Signature · 1 line
2.12.0.428.g67fe103aa
PATCH v8 6/6 stash: allow pathspecs in the no verb form
In reply to Thomas GummererNow that stash_push is used in the no verb form of stash, allow specifying the command line for this form as well. Always use -- to disambiguate pathspecs from other non-option arguments.
Also make git stash -p an alias for git stash push -p. This allows users to use git stash -p <pathspec>.
--- Documentation/git-stash.txt | 11 +++++++---- git-stash.sh | 3 +++ t/t3903-stash.sh | 15 +++++++++++++++ 3 files changed, 25 insertions(+), 4 deletions(-)
Documentation/git-stash.txt +7 -4
@@ -54,10 +54,13 @@ push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q Save your local modifications to a new 'stash' and roll them back to HEAD (in the working tree and in the index). The <message> part is optional and gives - the description along with the stashed state. For quickly making - a snapshot, you can omit _both_ "save" and <message>, but giving - only <message> does not trigger this action to prevent a misspelled - subcommand from making an unwanted stash. + the description along with the stashed state. ++ +For quickly making a snapshot, you can omit "push". In this mode, +non-option arguments are not allowed to prevent a misspelled +subcommand from making an unwanted stash. The two exceptions to this +are `stash -p` which acts as alias for `stash push -p` and pathspecs, +which are allowed after a double hyphen `--` for disambiguation. + When pathspec is given to 'git stash push', the new stash records the modified states only for the files that match the pathspec. The index
git-stash.sh +3 -0
@@ -657,12 +657,15 @@ apply_to_branch () { } } +test "$1" = "-p" && set "push" "$@" + PARSE_CACHE='--not-parsed' # The default command is "push" if nothing but options are given seen_non_option= for opt do case "$opt" in + --) break ;; -*) ;; *) seen_non_option=t; break ;; esac
t/t3903-stash.sh +15 -0
@@ -892,4 +892,19 @@ test_expect_success 'untracked files are left in place when -u is not given' ' test_path_is_file untracked ' +test_expect_success 'stash without verb with pathspec' ' + >"foo bar" && + >foo && + >bar && + git add foo* && + git stash -- "foo b*" && + test_path_is_missing "foo bar" && + test_path_is_file foo && + test_path_is_file bar && + git stash pop && + test_path_is_file "foo bar" && + test_path_is_file foo && + test_path_is_file bar +' + test_done
Signature · 1 line
2.12.0.428.g67fe103aa