From: Jonathan Nieder <jrnieder@gmail.com>
To: Dominik Salvet <dominik.salvet@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Fetch origin/HEAD during git fetch
Date: Tue, 8 Oct 2019 19:24:57 -0700 [thread overview]
Message-ID: <20191009022457.GB73710@google.com> (raw)
In-Reply-To: <CAEXP2g8-reK+u2FaO=mMP-nsvuDDWGpwV_tyKG5L5XpU=1LQeg@mail.gmail.com>
Hi!
Dominik Salvet wrote:
> 1) `git fetch origin && git remote set-head origin -a`
> 2) `git fetch origin +refs/heads/*:refs/remotes/origin/*
> HEAD:refs/remotes/origin/HEAD`
> 3) instead of git init and remote, use directly `git clone --no-checkout`
>
> The first solution is not suitable due its delay caused by remote
> access (2 separate invocations). For smaller repositories, delays of
> these individual commands are almost comparable. However, this
> solution is semantically exactly what I want.
Interesting.
For the specific case, it sounds like some kind of "git fetch
--also-set-head" would do the trick for you. As you can see, I'm awful
at naming command line options --- aside from the need to give it a
better name, any others thoughts on that? Would you be interested in
taking a stab at implementing it?
For the more general case, there's been some discussion of fetching
and pushing symrefs on-list before. [1] discusses one possible UI.
[...]
> The third solution has several problems. The first one is the created
> default local branch. So delete it.
Hm, I don't follow. Does "git checkout --orphan" do what you're
looking for?
Thanks and hope that helps,
Jonathan
[1] https://public-inbox.org/git/20180814214723.GA667@sigill.intra.peff.net/
next prev parent reply other threads:[~2019-10-09 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 1:37 Fetch origin/HEAD during git fetch Dominik Salvet
2019-10-09 2:24 ` Jonathan Nieder [this message]
2019-10-09 14:29 ` Dominik Salvet
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191009022457.GB73710@google.com \
--to=jrnieder@gmail.com \
--cc=dominik.salvet@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).