From: Cyrill Gorcunov <gorcunov@gmail.com>
To: git@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>
Subject: git remote branches oddies
Date: Mon, 23 Jun 2008 19:50:13 +0400 [thread overview]
Message-ID: <20080623155013.GD7094@cvg> (raw)
Hi git list,
could someone take a look please since I'm not
sure if that is right thing I'm doing with git ;)
I'm tracking a few linux kernel repos. Here is my git config:
--- git config ---
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "origin"]
url = git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
remote = origin
merge = refs/heads/master
[remote "x86"]
url = git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git
fetch = +refs/heads/*:refs/remotes/x86/*
[remote "tip"]
url = git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
fetch = +refs/heads/*:refs/remotes/tip/*
[gui]
geometry = 1037x445+260+116 207 192
[remote "udf"]
url = git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-udf-2.6.git
fetch = +refs/heads/*:refs/remotes/udf/*
------------------
By typing 'git remote update' I've got the following today
--- git remote update log ---
cyrill@cvg linux-2.6.git $ git remote update
Updating origin
Updating x86
From git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86
* [new branch] core/futexes -> x86/core/futexes
error: 'refs/remotes/x86/mm' exists; cannot create 'refs/remotes/x86/mm/xen'
* [new branch] mm/xen -> x86/mm/xen
d4abc23..ea71a54 sched-fixes-for-linus -> x86/sched-fixes-for-linus
error: unable to resolve reference refs/remotes/x86/sched/devel: Not a directory
* [new branch] sched/devel -> x86/sched/devel
error: unable to resolve reference refs/remotes/x86/sched/new-API-sched_setscheduler: Not a directory
* [new branch] sched/new-API-sched_setscheduler -> x86/sched/new-API-sched_setscheduler
error: unable to resolve reference refs/remotes/x86/sched/urgent: Not a directory
* [new branch] sched/urgent -> x86/sched/urgent
ffe6e1d..ebb9cfe x86-fixes-for-linus -> x86/x86-fixes-for-linus
error: Could not fetch x86
Updating tip
From git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip
* [new branch] core/futexes -> tip/core/futexes
d4abc23..ea71a54 sched-fixes-for-linus -> tip/sched-fixes-for-linus
error: unable to resolve reference refs/remotes/tip/sched/devel: Not a directory
* [new branch] sched/devel -> tip/sched/devel
error: unable to resolve reference refs/remotes/tip/sched/new-API-sched_setscheduler: Not a directory
* [new branch] sched/new-API-sched_setscheduler -> tip/sched/new-API-sched_setscheduler
error: unable to resolve reference refs/remotes/tip/sched/urgent: Not a directory
* [new branch] sched/urgent -> tip/sched/urgent
ffe6e1d..ebb9cfe x86-fixes-for-linus -> tip/x86-fixes-for-linus
error: Could not fetch tip
Updating udf
-----------------------------
I've asked Ingo what is happend with -tip tree. He answered:
| hm, this is due to a new 'sched/urgent' and 'sched/devel' branches being
| introduced, while the old ones were still around.
If I've recreated git repo from scratch - messages are gone. Not sure
how to react on this. Is that normal? (I would _not_ say that such
error messages annoying me but somehow a _bit_ unpleasant :-)
Please CC me since I'm not subscribed.
Btw the git I'm using is - git version 1.5.6.6.gd3e97.
- Cyrill -
reply other threads:[~2008-06-23 15:51 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=20080623155013.GD7094@cvg \
--to=gorcunov@gmail.com \
--cc=git@vger.kernel.org \
--cc=mingo@elte.hu \
/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).