git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* git remote branches oddies
@ 2008-06-23 15:50 Cyrill Gorcunov
  0 siblings, 0 replies; only message in thread
From: Cyrill Gorcunov @ 2008-06-23 15:50 UTC (permalink / raw)
  To: git; +Cc: Ingo Molnar

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 -

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2008-06-23 15:51 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-06-23 15:50 git remote branches oddies Cyrill Gorcunov

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).