From: Brian Foster <brian.foster@innova-card.com>
To: Tomas Carnecky <tom@dbservice.com>
Cc: git@vger.kernel.org
Subject: [SOLVED] `git fetch tag NAME' into mirror repo does not update HEAD, what to do?
Date: Thu, 12 Aug 2010 14:16:35 +0200 [thread overview]
Message-ID: <201008121416.35887.brian.foster@innova-card.com> (raw)
In-Reply-To: <4C63D579.507@dbservice.com>
On Thursday 12 August 2010 13:05:29 Tomas Carnecky wrote:
> On 8/12/10 12:38 PM, Brian Foster wrote:
> > On Thursday 12 August 2010 10:33:13 Tomas Carnecky wrote:
> >[ ... ]
> >> Fetch only fetches commits. It doesn't update any local refs (other than
> >> FETCH_HEAD). If you want to switch HEAD to that new tag, use checkout.
>
> Oh boy, that explanation is really bad -.- What I meant is that if
> you don't supply the <dst> part of the refspec it will only update
> FETCH_HEAD. So 'git fetch origin master' will not update anything
> but FETCH_HEAD.
I concur. However, the “refspec” in this case is the obscure
‘tag TAGNAME’ (where the ‘tag’ is a keyword); see get-fetch(1)
at the end of §OPTIONS where it describes “short-cut notations”.
That does not seem to accept a :<dst>, nor would I be too sure
what it meant if it did.
> > No, a fetch in a mirror, when fetching all the way
> > to the HEAD (e.g., a simple `git fetch origin'),
> > does update the branch. [ ... ]
>
> There are different ways to invoke git fetch. Either way, fetch will
> never modify HEAD. However, it can modify the branch that HEAD is
> pointing to (in case HEAD is a symref).
Point taken, I was being sloppy. We want the head of the
relevant branch (master) to be updated in our bare (mirror)
repository.
> But you are not fetching a
> branch, you are fetching a tag. So you need to use checkout after you
> fetch it. Either 'git checkout FETCH_HEAD' or 'git checkout v2'.
NO. ‘get checkout ...’ does not work in a bare repository.
(You can modify my trivial posted script to prove this.)
However, your comment got me to thinking. This _does_ work:
git reset --soft FETCH_HEAD
(And, I presume without testing, so would ‘... v2’ ?)
Given that git-reset(1)'s purpose is to change the branch's
head (or to change HEAD as I've been incorrectly describing
it), that does make sense.
cheers!
-blf-
next prev parent reply other threads:[~2010-08-12 12:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 7:54 [Q] `git fetch tag NAME' into mirror repo does not update HEAD, what to do? Brian Foster
2010-08-12 8:33 ` Tomas Carnecky
2010-08-12 10:38 ` Brian Foster
2010-08-12 11:05 ` Tomas Carnecky
2010-08-12 12:16 ` Brian Foster [this message]
2010-08-12 12:32 ` [SOLVED] " Tomas Carnecky
2010-08-12 13:22 ` Brian Foster
2010-08-12 13:34 ` Tomas Carnecky
2010-08-13 7:03 ` Brian Foster
2010-08-12 17:02 ` [Q] " Brandon Casey
2010-08-13 7:22 ` Brian Foster
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=201008121416.35887.brian.foster@innova-card.com \
--to=brian.foster@innova-card.com \
--cc=git@vger.kernel.org \
--cc=tom@dbservice.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.
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).