All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gummerer <t.gummerer@gmail.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2017, #05; Tue, 24)
Date: Thu, 26 Oct 2017 21:53:01 +0100	[thread overview]
Message-ID: <20171026205301.GA13767@hank> (raw)
In-Reply-To: <7b40d574-c6e3-d824-5e2f-b7cf18dadeb5@ramsayjones.plus.com>

On 10/26, Ramsay Jones wrote:
> 
> 
> 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 about this.  Would indeed be great if we could still fix it.
Thanks for catching this.

> [Sorry for not spotting this earlier; I only noticed when doing an
> 'git log --oneline' display which, naturally, puts focus on the
> subject lines. ;-) ]
> 
> ATB,
> Ramsay Jones
> 
> 

  reply	other threads:[~2017-10-26 20:51 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 [this message]
2017-10-27  1:02   ` Junio C Hamano

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=20171026205301.GA13767@hank \
    --to=t.gummerer@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=ramsay@ramsayjones.plus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.