From: Matthieu Imbert <matthieu.imbert@inria.fr>
To: git@vger.kernel.org
Subject: remote branches
Date: Sun, 13 Feb 2011 08:42:37 +0100 [thread overview]
Message-ID: <4D578B6D.9090803@inria.fr> (raw)
hi.
I have troubles (probably due to my misunderstanding) with git remote
tracking branches. It seems to me that reality and documentation are
different:
- i clone the linux git repo:
$ git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
linux-2.6.git
- then i add a remote tracking branch:
$ git remote add --tags drm-intel
git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel.git
- Then i do git fetch or git fetch drm-intel, but nothing happens, and
git branch -r still only show me origin/HEAD and origin/master, no
drm-intel branches, though these branches do exist since i can see them
with git remote -v show drm-intel
what am i doing wrong here, any idea?
cheers,
--
Matthieu
next reply other threads:[~2011-02-13 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 7:42 Matthieu Imbert [this message]
2011-02-13 9:17 ` remote branches Ævar Arnfjörð Bjarmason
2011-02-13 10:07 ` Matthieu Imbert
2011-02-13 10:08 ` Andreas Schwab
2011-02-13 10:13 ` Matthieu Imbert
2011-02-13 10:31 ` Björn Steinbrink
2011-02-14 6:12 ` Junio C Hamano
2011-02-16 18:00 ` Christian Jaeger
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=4D578B6D.9090803@inria.fr \
--to=matthieu.imbert@inria.fr \
--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).