1

The stash "push" command is really practical, while stash "save" is supposed to be deprecated. However, on magit I can just find stash save... Is there any reason for that? Did I miss something?

Switches -u Also save untracked files (--include-untracked) -a Also save untracked and ignored files (--all) Actions z Save Z Snapshot p Pop i Save index I Snapshot index a Apply w Save worktree W Snapshot worktree l List x Save keeping index r Snapshot to wipref v Show b Branch k Drop f Format patch 

Thank you.

3
  • It's deprecated with the commit fd2ebf14db52c, which follows v2.15.0-rc2. Given that the current git is 2.16.1, as of this writing, Magit author needs a bit of time to fix it up. Meanwhile, you could fill an issue on github to help him track it. Commented Jan 30, 2018 at 1:41
  • Remember that Magit supports Git versions 1.9.4 and above. Commented Jan 30, 2018 at 2:37
  • Oh, I though it was older than that. I filled as you proposed an issue here github.com/magit/magit/issues/3349 Commented Jan 30, 2018 at 2:45

1 Answer 1

3

(Answering based on https://github.com/magit/magit/issues/3349 )

From my reading, the single difference of note between git stash save and git stash push is the ability to include optional <pathspec> arguments in the latter.

You can already achieve this effect in Magit by staging the things you wish to stash, and then stashing the index.

(n.b. Magit implements its own custom stashing features, including stashing just the index, or just the un-staged changes.)

As git stash push also (apparently) utilises the index, it doesn't look like Magit has anything to gain by using stash push.

1
  • Thanks! I was also thinking that magit was using deprecated stuff, but in fact it seems that magit just implemented stash save without using stash save... So no problem. Thanks! Commented Feb 2, 2018 at 9:33

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.