From: Harald Nordgren <haraldnordgren@gmail.com>
To: ben.knoble@gmail.com
Cc: git@vger.kernel.org, gitgitgadget@gmail.com, haraldnordgren@gmail.com
Subject: gh
Date: Sat, 25 Apr 2026 20:07:49 +0200 [thread overview]
Message-ID: <20260425180749.49933-1-haraldnordgren@gmail.com> (raw)
In-Reply-To: <6F9060F0-20EB-4B60-8677-86DA2AB39B35@gmail.com>
> I’m not totally opposed to this convenience, but couldn’t we also just teach gh to run set-head as a second command?
We probably could, and maybe we should.
One argument for this new options is that I believe 'git clone' has this
behavior, so it's attractive if forking (adding a secondary remote) could
work in the same way as clone (adding the first remote).
Harald
next prev parent reply other threads:[~2026-04-25 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-25 11:19 [PATCH] remote: add --set-head option to 'git remote add' Harald Nordgren via GitGitGadget
2026-04-25 17:20 ` Ben Knoble
2026-04-25 18:07 ` Harald Nordgren [this message]
2026-04-25 21:58 ` Junio C Hamano
2026-04-25 22:06 ` Jeff King
2026-04-26 8:21 ` Harald Nordgren
-- strict thread matches above, loose matches on Subject: below --
2026-04-25 21:57 Multiple remotes Ben Knoble
2026-04-25 22:54 ` gh Harald Nordgren
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=20260425180749.49933-1-haraldnordgren@gmail.com \
--to=haraldnordgren@gmail.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@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