From: Rene Herman <rene.herman@gmail.com>
To: git@vger.kernel.org
Subject: tags "problem"
Date: Fri, 14 Sep 2007 21:31:21 +0200 [thread overview]
Message-ID: <46EAE189.5000804@gmail.com> (raw)
Hi people.
(please keep me in CC)
Was just busy constructing a tree and noticed a "problem" -- no doubt caused
by me, but help appreciated.
I clone linus' kernel tree into ./local, then do a
git checkout -b v22 v2.6.22
to get a 2.6.22 branch. I like to have a simple "git pull" while on this
branch pull from the upstream stable tree, so as advised earlier, I put:
[branch "v22"]
remote = linux-2.6.22.y
merge = refs/heads/master
[remote "linux-2.6.22.y"]
url =
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.22.y.git
fetch = refs/heads/master
in ./git/config. "git pull" now indeed works nicely.
I just noticed now though that this doesn't automatiically fetches tags as
well. That is, no v2.6.22.x tags after that. "git fetch --tags" (or git pull
--tags directly, I assume) gets them without problem, but I was expecting
they'd be fetched automatically.
Should they? Can they? Can I put anything in the config so they will?
Rene.
next reply other threads:[~2007-09-14 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 19:31 Rene Herman [this message]
2007-09-14 21:14 ` tags "problem" Junio C Hamano
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=46EAE189.5000804@gmail.com \
--to=rene.herman@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.