Thread (1 message) 1 message, 1 author, 2017-10-27

Re: What's cooking in git.git (Oct 2017, #05; Tue, 24)

From: Junio C Hamano <hidden>
Date: 2017-10-27 01:02:16

Ramsay Jones [off-list ref] writes:
On 24/10/17 06:28, Junio C Hamano wrote:
[snip]> 
quoted
* tg/deprecate-stash-save (2017-10-23) 3 commits
 - stash: remove now superfluos help for "stash push"
 - mark git stash push deprecated in the man page
 - replace git stash save with git stash push in the documentation

 "git stash save" has been deprecated in favour of "git stash push".

 Will merge to 'next'.
If you don't intend to include this in v2.15.0, when re-building
the next branch after release (the above is now in 'next'), could
we please remember to update one of the commit message subject line.

In particular, commit 742d6ce35b ("mark git stash push deprecated
in the man page", 22-10-2017), is marking 'git stash *save*' as
deprecated, not *push*.

[Sorry for not spotting this earlier; I only noticed when doing an
'git log --oneline' display which, naturally, puts focus on the
subject lines. ;-) ]
Thanks for spotting.  I can always revert the merge into 'next' and
then merge a rewritten copy of the series back into 'next' again to
preserve the fast-forwardness of the integration branch, so that I
do not have to remember ;-)
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help