git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: git <git@vger.kernel.org>
Subject: remote.branch.tagopts = --tags not updating branches
Date: Sat, 02 Jun 2012 11:54:26 +0200	[thread overview]
Message-ID: <4FC9E2D2.5060705@dewire.com> (raw)

For some reason I had tagopt set in a remote of mine. The drawback
is that it does not update any remote refs.

[remote "gerrit"]
         url = git://git.eclipse.org/gitroot/jgit/jgit
         fetch = +refs/heads/*:refs/remotes/gerrit/*
         fetch = +refs/changes/*:refs/remotes/gerrit/changes/*
         tagopt = --tags

First force a remote ref to become "old", then update it with C Git (nothing happens).
Them update for real with JGit.

$ git update-ref refs/remotes/gerrit/stable-2.0 058c74d8adcfb5ef0eed203a64b7f9ff65e87c8c
$ git fetch gerrit
$ jgit fetch gerrit
Updating references:    100% (1/1)
 From git://git.eclipse.org/gitroot/jgit/jgit
    058c74d..23b8136  stable-2.0 -> gerrit/stable-2.0

 From the docs I cannot see that Git is supposed to behave this way. The man pages
only mention the effects of this option on tags.

-- robin

                 reply	other threads:[~2012-06-02 10:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4FC9E2D2.5060705@dewire.com \
    --to=robin.rosenberg.lists@dewire.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).