From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Bence Ferdinandy" <bence@ferdinandy.com>, git@vger.kernel.org
Subject: Re: [RFC PATCH] object-name: add @{upstreamhead} shorthand
Date: Sun, 20 Oct 2024 22:40:27 +0200 [thread overview]
Message-ID: <1c056d39-950c-4965-89d6-85f0c2c1bccd@app.fastmail.com> (raw)
In-Reply-To: <20241020202507.2596990-1-bence@ferdinandy.com>
Good evening
On Sun, Oct 20, 2024, at 22:24, Bence Ferdinandy wrote:
> The HEAD of the remote is useful in many situations, but currently one
> would need to know the name of the remote to perform something like
> "git log origin/HEAD..", which makes writing remote agnostic aliases
> complicated. Introduce the new shorthand "@{upstreamhead}" which returns
> <remote>/HEAD for the same <remote> "@{upstream}" would yield.
>
> Signed-off-by: Bence Ferdinandy <bence@ferdinandy.com>
> ---
>
> Notes:
> RFC v1: Testing and documentation is completely missing, I'll add those
> in a v2 if people think the patch has merit.
Do you have some concrete examples? I’m not well versed in using
remote HEAD.
--
Kristoffer Haugsbakk
next prev parent reply other threads:[~2024-10-20 20:40 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 [this message]
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
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=1c056d39-950c-4965-89d6-85f0c2c1bccd@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=bence@ferdinandy.com \
--cc=git@vger.kernel.org \
/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).