From: Brian Foster <brian.foster@innova-card.com>
To: Tomas Carnecky <tom@dbservice.com>
Cc: git@vger.kernel.org
Subject: Re: [SOLVED] `git fetch tag NAME' into mirror repo does not update HEAD, what to do?
Date: Fri, 13 Aug 2010 09:03:56 +0200 [thread overview]
Message-ID: <201008130903.56375.brian.foster@innova-card.com> (raw)
In-Reply-To: <4C63F860.2090600@dbservice.com>
On Thursday 12 August 2010 15:34:24 Tomas Carnecky wrote:
> On 8/12/10 3:22 PM, Brian Foster wrote:
> > On Thursday 12 August 2010 14:32:41 Tomas Carnecky wrote:
> >> When you use
> >> 'git update-ref --no-deref HEAD v2' it will modify HEAD
> >
> > NO, it gets an error [ ... ]
>
> Oh the subtleties when working with plumbing:
> git update-ref --no-deref HEAD v2^{commit}
Yes, that updates HEAD, leaving SLAVE in the odd state
of HEAD being v2 and master's head being v1 (which I
presume is another example of detached head?).
> >[ ... ]
> > I do_not_ want a detached head! This has perhaps been
> > confused by my improperly saying “update HEAD” when I
> > meant “update the master branch”. [ ... ]
> > Having HEAD continue to
> > be a symref to refs/heads/master (which, in this case,
> > is the same commit as v2) is correct.
>
> Just make sure your tools and scripts don't break when you reset the
> branch like that (especially when the update is non-fast forward as
> fetch+reset won't warn you when this happens).
Understood. And I'm not too worried about that happening,
albeit the current procedures are perhaps not as robust as
they could or should be. Again, thanks for the suggestions
and help.
cheers!
-blf-
next prev parent reply other threads:[~2010-08-13 7:04 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 ` [SOLVED] " Brian Foster
2010-08-12 12:32 ` Tomas Carnecky
2010-08-12 13:22 ` Brian Foster
2010-08-12 13:34 ` Tomas Carnecky
2010-08-13 7:03 ` Brian Foster [this message]
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=201008130903.56375.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).