From: Junio C Hamano <gitster@pobox•com>
To: Ramsay Jones <ramsay@ramsayjones•plus.com>
Cc: git@vger•kernel.org, Thomas Gummerer <t.gummerer@gmail•com>
Subject: Re: What's cooking in git.git (Oct 2017, #05; Tue, 24)
Date: Fri, 27 Oct 2017 10:02:08 +0900 [thread overview]
Message-ID: <xmqqlgjxe73j.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <7b40d574-c6e3-d824-5e2f-b7cf18dadeb5@ramsayjones.plus.com> (Ramsay Jones's message of "Thu, 26 Oct 2017 17:44:54 +0100")
Ramsay Jones <ramsay@ramsayjones•plus.com> writes:
> On 24/10/17 06:28, Junio C Hamano wrote:
> [snip]>
>> * 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 ;-)
prev parent reply other threads:[~2017-10-27 1:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 5:28 What's cooking in git.git (Oct 2017, #05; Tue, 24) Junio C Hamano
2017-10-26 16:44 ` Ramsay Jones
2017-10-26 20:53 ` Thomas Gummerer
2017-10-27 1:02 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqlgjxe73j.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=ramsay@ramsayjones$(echo .)plus.com \
--cc=t.gummerer@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox