From: Tim Jaacks <tim.jaacks@garz-fricke.com>
To: "René Scharfe" <l.s.r@web.de>, "Chris Torek" <chris.torek@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: AW: git diff ^! syntax stopped working for stashes in Git 2.28
Date: Wed, 28 Sep 2022 09:02:42 +0000 [thread overview]
Message-ID: <15f30d59650b4de2b14d89f6e8cb21ce@garz-fricke.com> (raw)
In-Reply-To: <70e87095-d8be-f859-f5b4-a5e15904149c@web.de>
Hey Chris, hey René,
thanks a lot for your replys.
> So, Tim, does `git stash show -p stash@{0}` work for you?
Yes, that works indeed. However, in my certain use-case I would prefer using `git diff`.
> Letting `git diff X^!` mean the same as `git diff X ^X^` for a non-merge
> makes sense to me given the definition from gitrevisions(7) cited above.
> That in turn is the same as `git diff X^..X` and `git diff X^ X`.
Yes, that is exactly how it worked before. And all the other syntaxes still work correctly.
René, I saw you submitted some patches already, but these weren't approved obviously. So how does this continue now?
Kind regards,
Tim
--
Tim Jaacks
SOFTWARE DEVELOPER
SECO Northern Europe GmbH
Schlachthofstrasse 20
21079 Hamburg
Germany
T: +49 40 791899-183
E: tim.jaacks@seco.com
Registergericht: Amtsgericht Hamburg, HRB 148893
Geschäftsführer: Stefan Heczko, Marc-Michael Braun, Massimo Mauri
next prev parent reply other threads:[~2022-09-28 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 9:57 git diff ^! syntax stopped working for stashes in Git 2.28 Tim Jaacks
2022-09-12 11:16 ` René Scharfe
2022-09-12 19:09 ` Chris Torek
2022-09-14 15:57 ` René Scharfe
2022-09-28 9:02 ` Tim Jaacks [this message]
2022-09-28 17:39 ` René Scharfe
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=15f30d59650b4de2b14d89f6e8cb21ce@garz-fricke.com \
--to=tim.jaacks@garz-fricke.com \
--cc=chris.torek@gmail.com \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
/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).