From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "Martin Ågren" <martin.agren@gmail.com>
Cc: Git Mailing list <git@vger.kernel.org>
Subject: Re: error(?) in "man git-stash" regarding "--keep-index"
Date: Fri, 18 May 2018 06:51:27 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.1805180648020.10270@localhost.localdomain> (raw)
In-Reply-To: <CAN0heSrJMFij9xt6RstLD16+2CxJ_HALer4iRL74AZQvH0VWRQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1959 bytes --]
On Fri, 18 May 2018, Martin Ågren wrote:
> On 18 May 2018 at 11:37, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> >
> > toward the bottom of "man git-stash", one reads part of an example:
> >
> > # ... hack hack hack ...
> > $ git add --patch foo # add just first part to the index
> > $ git stash push --keep-index # save all other changes to the stash
> > ^^^^^ ???
> >
> > i thought that, even if "--keep-index" left staged changes in the
> > index, it still included those staged changes in the stash. that's
> > not the impression one gets from the above.
>
> So would the error be in the part of the man-page quoted below?
>
> If the --keep-index option is used, all changes already added to
> the index are left intact.
no, that part is correct, it clearly(?) states that staged changes
are left where they are, in the index. i submit that the misleading
part is in the example i quoted, which suggests that only the "other"
changes are saved to the stash -- that is, the changes other than what
is already in the index.
> That is, this doesn't say *where* things are left intact (in the
> index? in the working tree?).
in that case, that's something that could obviously be clarified.
> The man-page does start with
>
> git-stash - Stash the changes in a dirty working directory away
>
> which to me suggests that "leaving something intact" refers to
> precisely this -- the working directory.
>
> Or is it the name of the option that trips you up? That is, you read
> the name as `--keep-the-index-as-is-but-stash-as-usual`, as opposed
> to `--keep-what-is-already-in-the-index-around`?
>
> While I'm sure that some clarification could be provided, I'm tempted to
> argue that is exactly what the example provides that you quoted from.
i guess we can agree to disagree, since i think the snippet of the
example i provided gives a misleading explanation.
rday
next prev parent reply other threads:[~2018-05-18 10:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 9:37 error(?) in "man git-stash" regarding "--keep-index" Robert P. J. Day
2018-05-18 10:41 ` Martin Ågren
2018-05-18 10:51 ` Robert P. J. Day [this message]
2018-05-18 12:25 ` Martin Ågren
2018-05-18 15:37 ` Sybille Peters
2018-05-18 15:43 ` Robert P. J. Day
2018-05-18 17:14 ` Martin Ågren
2018-05-19 10:05 ` Sybille Peters
2018-05-18 20:24 ` Robert P. J. Day
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=alpine.LFD.2.21.1805180648020.10270@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=git@vger.kernel.org \
--cc=martin.agren@gmail.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 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 NNTP newsgroup(s).