From: Jeff King <peff@peff.net>
To: Dror Livne <dror.livne@mobileye.com>
Cc: git@vger.kernel.org
Subject: Re: Fetch and refs/remotes/<refname>/HEAD
Date: Sun, 9 Aug 2015 19:23:31 -0400 [thread overview]
Message-ID: <20150809232330.GA25769@sigill.intra.peff.net> (raw)
In-Reply-To: <loom.20150803T151815-131@post.gmane.org>
On Mon, Aug 03, 2015 at 01:28:05PM +0000, Dror Livne wrote:
> I have noticed that when cloning a repository, I get a
> refs/remotes/origin/HEAD symbolic ref.
>
> On the other hand, when fetching a new remote, the remote HEAD is not set by
> git-fetch (but can be added later by `git remote set-head ...')
>
> I was under the impression that clone is equivalent to (at least) init+fetch.
>
> Is there a rationale for that difference in behavior?
I have been annoyed by this in the past, too. There's no real reason,
except that setting up the symref is outside the scope of "fetch".
Fetching is just about updating refs, and we explicitly do not want
subsequent fetches to overwrite any changes you might make to
refs/remotes/.../HEAD.
Setting up the remote HEAD symref more rightly belongs to "git remote
add", but that program does not otherwise talk to the remote. And that's
why we end up with the separate set-head step. It might make sense for
"git remote add -f" to automatically run "set-head", since it is
contacting the remote server already. And then:
git init
git remote add -f origin ...
would be similar to "git clone".
-Peff
prev parent reply other threads:[~2015-08-09 23:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 13:28 Fetch and refs/remotes/<refname>/HEAD Dror Livne
2015-08-09 23:23 ` Jeff King [this message]
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=20150809232330.GA25769@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=dror.livne@mobileye.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).