git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Igor Djordjevic'" <igor.d.djordjevic@gmail.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 14:30:23 -0400	[thread overview]
Message-ID: <000c01d2e2e0$cda526b0$68ef7410$@nexbridge.com> (raw)
In-Reply-To: <11f1877a-6ec3-02c1-5b06-c1a07a389010@gmail.com>

On June 11, 2017 2:19 PM  Igor Djordjevic wrote: 
>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.

I'm sorry for not checking first before posting. Thanks 😊

Randall


  reply	other threads:[~2017-06-11 18:30 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
2017-06-11 18:30             ` Randall S. Becker [this message]
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='000c01d2e2e0$cda526b0$68ef7410$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    --cc=houstonfortney@gmail.com \
    --cc=igor.d.djordjevic@gmail.com \
    --cc=liambeguin@gmail.com \
    --cc=peff@peff.net \
    --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).