From: Timur Tabi <timur@freescale.com>
To: git@vger.kernel.org
Subject: Did I miss something? git-clone doesn't grab all branches????
Date: Fri, 30 Mar 2007 10:57:34 -0500 [thread overview]
Message-ID: <460D336E.9040708@freescale.com> (raw)
I used to be able to do this:
git-clone http://ftp.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git
cd powerpc
git-checkout for-2.6.22
But that doesn't work any more. Why not? It was working perfectly fine before.
So someone told me I need to do this:
git-clone http://ftp.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git
cd powerpc
git-fetch http://www.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git
for-2.6.22:for-2.6.22
git-checkout for-2.6.22
Ok, fine, but now when I do git-pull, I get this:
[snip]
* refs/remotes/origin/merge: fast forward to branch 'merge' of
http://ftp.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc
old..new: e0f2e3a..190a440
Warning: No merge candidate found because value of config option
"branch.for-2.6.22.merge" does not match any remote branch fetched.
No changes.
What does the warning mean? And why is it so difficult to clone branches now?
--
Timur Tabi
Linux Kernel Developer @ Freescale
next reply other threads:[~2007-03-30 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 15:57 Timur Tabi [this message]
2007-03-30 16:30 ` Did I miss something? git-clone doesn't grab all branches???? Loeliger Jon-LOELIGER
2007-03-30 17:03 ` Timur Tabi
2007-03-31 1:30 ` 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=460D336E.9040708@freescale.com \
--to=timur@freescale.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).