From: 小川恭史 <aiueogawa217@gmail.com>
To: Junio C Hamano <gitster@pobox.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 12:52:36 +0900 [thread overview]
Message-ID: <CAC2Jkr+zFy9q4Xnzxcqj6rq9+TOs2sO9J5Wx9ccd3oiY4N20uA@mail.gmail.com> (raw)
In-Reply-To: <CAC2Jkr+ZDUxd9JcKvVwZqCHVW+Bpp2CbdyehwgKV_Ru-Uqxo8A@mail.gmail.com>
As you point,
git stash
without any argument is equivalent to both of
git stash save
git stash push
. The original sentence is correct.
2017-10-12 12:31 GMT+09:00 小川恭史 <aiueogawa217@gmail.com>:
> As you point,
>
> git stash
>
> without any argument is equivalent to both of
> git stash save and
>
>
> 2017-10-12 9:53 GMT+09:00 Junio C Hamano <gitster@pobox.com>:
>> 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 3:52 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
[not found] ` <CAC2Jkr+ZDUxd9JcKvVwZqCHVW+Bpp2CbdyehwgKV_Ru-Uqxo8A@mail.gmail.com>
2017-10-12 3:52 ` 小川恭史 [this message]
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
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=CAC2Jkr+zFy9q4Xnzxcqj6rq9+TOs2sO9J5Wx9ccd3oiY4N20uA@mail.gmail.com \
--to=aiueogawa217@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).