From: Taylor Blau <me@ttaylorr.com>
To: Bence Ferdinandy <bence@ferdinandy.com>
Cc: Jeff King <peff@peff.net>,
Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
git@vger.kernel.org
Subject: Re: [RFC PATCH] object-name: add @{upstreamhead} shorthand
Date: Mon, 21 Oct 2024 16:35:11 -0400 [thread overview]
Message-ID: <Zxa6/4D8lWgqqaxM@nand.local> (raw)
In-Reply-To: <D51R90BTHJMY.1C1XY5P4CHTWG@ferdinandy.com>
On Mon, Oct 21, 2024 at 10:09:38PM +0200, Bence Ferdinandy wrote:
> > E.g., I think you could do:
> >
> > upstream=$(git rev-parse --symbolic-full-name @{upstream})
> > git log ${upstream%/*}/HEAD..
>
> That particular one will break if you have something like
> refs/remotes/origin/foo/bar, but I get your point.
Ugh. Having / characters in remote names feels like a mistake to me ;-).
Thanks,
Taylor
next prev parent reply other threads:[~2024-10-21 20:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 20:24 [RFC PATCH] object-name: add @{upstreamhead} shorthand Bence Ferdinandy
2024-10-20 20:40 ` Kristoffer Haugsbakk
2024-10-20 21:42 ` Bence Ferdinandy
2024-10-21 19:14 ` Jeff King
2024-10-21 20:09 ` Bence Ferdinandy
2024-10-21 20:35 ` Taylor Blau [this message]
2024-10-23 21:56 ` Jeff King
2024-10-24 18:48 ` Bence Ferdinandy
2024-10-25 6:24 ` Jeff King
2024-10-27 22:07 ` Bence Ferdinandy
2024-10-27 23:45 ` Taylor Blau
2024-10-28 5:33 ` Jeff King
2024-10-21 19:45 ` Taylor Blau
2024-10-21 20:11 ` Bence Ferdinandy
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=Zxa6/4D8lWgqqaxM@nand.local \
--to=me@ttaylorr.com \
--cc=bence@ferdinandy.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=peff@peff.net \
/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).