From: Junio C Hamano <gitster@pobox•com>
To: Takahito Ogawa <aiueogawa217@gmail•com>
Cc: git@vger•kernel.org, Takahito Ogawa <takahito.ogawa@datagrid•co.jp>
Subject: Re: [PATCH 1/1] git-stash.txt: correct "git stash" behavior with no arguments
Date: Thu, 12 Oct 2017 09:53:56 +0900 [thread overview]
Message-ID: <xmqqr2u92nkr.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20171011180350.99888-1-takahito.ogawa@datagrid.co.jp> (Takahito Ogawa's message of "Thu, 12 Oct 2017 03:03:50 +0900")
Takahito Ogawa <aiueogawa217@gmail•com> writes:
> @@ -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`.
Hmph. Is there any difference between
git stash save
git stash push
without any other argument? Aren't they equivalent to
git stash
without any argument, which is what this sentence explains?
next prev parent reply other threads:[~2017-10-12 0:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 18:03 [PATCH 1/1] git-stash.txt: correct "git stash" behavior with no arguments Takahito Ogawa
2017-10-12 0:53 ` Junio C Hamano [this message]
[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
-- strict thread matches above, loose matches on Subject: below --
2017-10-11 18:06 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 20:01 Takahito Ogawa
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=xmqqr2u92nkr.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=aiueogawa217@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=takahito.ogawa@datagrid$(echo .)co.jp \
/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