git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Takahito Ogawa <aiueogawa217@gmail.com>
To: git@vger.kernel.org
Cc: Takahito Ogawa <takahito.ogawa@datagrid.co.jp>
Subject: [PATCH 1/1] git-stash.txt: correct "git stash" behavior with no arguments
Date: Thu, 12 Oct 2017 03:06:27 +0900	[thread overview]
Message-ID: <20171011180627.153-1-takahito.ogawa@datagrid.co.jp> (raw)
In-Reply-To: <n>

"git stash" behavior without any arguments was changed in
1ada5020b ("stash: use stash_push for no verb form", 2017-02-28).
This is equivalent to "git stash push" but document says
"git stash save".

Correct it.

Signed-off-by: Takahito Ogawa <takahito.ogawa@datagrid.co.jp>
---
 Documentation/git-stash.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/git-stash.txt b/Documentation/git-stash.txt
index 00f95fee1..63642c145 100644
--- a/Documentation/git-stash.txt
+++ b/Documentation/git-stash.txt
@@ -33,7 +33,7 @@ and reverts the working directory to match the `HEAD` commit.
 The modifications stashed away by this command can be listed with
 `git stash list`, inspected with `git stash show`, and restored
 (potentially on top of a different commit) with `git stash apply`.
-Calling `git stash` without any arguments is equivalent to `git stash save`.
+Calling `git stash` without any arguments is equivalent to `git stash push`.
 A stash is by default listed as "WIP on 'branchname' ...", but
 you can give a more descriptive message on the command line when
 you create one.
-- 
2.13.1


             reply	other threads:[~2017-10-11 18:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11 18:06 Takahito Ogawa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-10-11 20:01 [PATCH 1/1] git-stash.txt: correct "git stash" behavior with no arguments Takahito Ogawa
2017-10-11 18:37 Takahito Ogawa
2017-10-11 19:09 ` Thomas Gummerer
2017-10-11 19:12   ` Thomas Gummerer
2017-10-11 18:03 Takahito Ogawa
2017-10-12  0:53 ` Junio C Hamano
     [not found]   ` <CAC2Jkr+ZDUxd9JcKvVwZqCHVW+Bpp2CbdyehwgKV_Ru-Uqxo8A@mail.gmail.com>
2017-10-12  3:52     ` 小川恭史
2017-10-12  3:54       ` 小川恭史
2017-10-12  9:56         ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171011180627.153-1-takahito.ogawa@datagrid.co.jp \
    --to=aiueogawa217@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=takahito.ogawa@datagrid.co.jp \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).