git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Igor Djordjevic <igor.d.djordjevic@gmail.com>
To: "Randall S. Becker" <rsbecker@nexbridge.com>,
	'liam Beguin' <liambeguin@gmail.com>, 'Jeff King' <peff@peff.net>,
	'Samuel Lijin' <sxlijin@gmail.com>
Cc: 'Houston Fortney' <houstonfortney@gmail.com>, git@vger.kernel.org
Subject: Re: Feature Request: Show status of the stash in git status command
Date: Sun, 11 Jun 2017 20:18:33 +0200	[thread overview]
Message-ID: <11f1877a-6ec3-02c1-5b06-c1a07a389010@gmail.com> (raw)
In-Reply-To: <000b01d2e2dc$327c11c0$97743540$@nexbridge.com>

Hi Randall,

On 11/06/2017 19:57, Randall S. Becker wrote:
> Random thought: what if a stash id could be used in the same way as 
> any other ref, so diff stash[0] stash[1] would be possible - 
> although I can see this being problematic for a merge or rebase.

Not sure if I`m misunderstanding you, but at least `git diff 
stash@{0} stash@{1}` seems to already work as expected - I remember 
using it in the past, and I`ve tried it again now[1], and it still 
works.

[1] git version 2.13.0.windows.1

Regards,
Buga

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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07 22:46 Feature Request: Show status of the stash in git status command Houston Fortney
2017-06-10  8:25 ` Jeff King
2017-06-10 10:12   ` Samuel Lijin
2017-06-10 10:22     ` Jeff King
2017-06-11 17:07       ` liam Beguin
2017-06-11 17:57         ` Randall S. Becker
2017-06-11 18:18           ` Igor Djordjevic [this message]
2017-06-11 18:30             ` Randall S. Becker
2017-06-12 15:35         ` Junio C Hamano
2017-06-13  3:42           ` liam Beguin
2017-06-13  6:42             ` Konstantin Khomoutov
2017-06-13 12:34               ` liam Beguin
2017-06-13 13:06                 ` 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=11f1877a-6ec3-02c1-5b06-c1a07a389010@gmail.com \
    --to=igor.d.djordjevic@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=houstonfortney@gmail.com \
    --cc=liambeguin@gmail.com \
    --cc=peff@peff.net \
    --cc=rsbecker@nexbridge.com \
    --cc=sxlijin@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).