Re: [PATCH 2/1] mention git stash push first in the man page
- From
Jeff King <peff@peff.net>
- Date
- Oct 21, 2017, 06:20 UTC
- Message-ID
- <20171021062050.wp2fdjwmjhwcorln@sigill.intra.peff.net>
- In-Reply-To
- <alpine.LFD.2.21.1710200403260.30185@localhost.localdomain>
On Fri, Oct 20, 2017 at 04:04:10AM -0400, Robert P. J. Day wrote:
Show 9 quoted lines
> > > I don't think there's any reason to go slow in marking something as > > > deprecated. It's the part where we follow up and remove or change the > > > feature that must take a while. > > > > Makes sense, let me drop it from the synopsis then. > > what, exactly, is the oft-referred-to issue with how "git stash > save" works that is being addressed with the new syntax of "git stash > push"?
"stash save" soaks up all arguments as the stash message, so it's not possible to specify pathspecs. "push" uses "-m <msg>" for the stash message, and can accept pathspecs.
-Peff