git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Bence Ferdinandy <bence@ferdinandy.com>
Cc: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
	git@vger.kernel.org
Subject: Re: [RFC PATCH] object-name: add @{upstreamhead} shorthand
Date: Mon, 21 Oct 2024 15:45:26 -0400	[thread overview]
Message-ID: <ZxavVmjsshVHCPcL@nand.local> (raw)
In-Reply-To: <D50YLOBHJTLS.367TMAOLKL019@ferdinandy.com>

On Sun, Oct 20, 2024 at 11:42:38PM +0200, Bence Ferdinandy wrote:
> But so the long story short here is that for
> (origin|upstream)/(master|main|trunk) we can already have agnostic code with
> HEAD for the second part and with a patch like this we could have agnostic code
> for the whole thing.

I'm hesitant to pick this up because of what is said in this paragraph.
When you write "(master|main|trunk)", I think you're really spelling
"HEAD". And it's fine to write HEAD in a script when you want to resolve
something to master/main/trunk/etc. without caring which and instead
delegating that to whatever the remote HEAD is.

But determining the upstream of a branch is already easy to do as Peff
points out downthread. So this seems like a band-aid for scripts that do
not care to perform such a resolution themselves.

Thanks,
Taylor

  parent reply	other threads:[~2024-10-21 19:45 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
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 [this message]
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=ZxavVmjsshVHCPcL@nand.local \
    --to=me@ttaylorr.com \
    --cc=bence@ferdinandy.com \
    --cc=git@vger.kernel.org \
    --cc=kristofferhaugsbakk@fastmail.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).