From: Larry Finger <Larry.Finger@lwfinger.net>
To: John Linville <linville@tuxdriver.com>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Problem with wireless-2.6
Date: Mon, 05 Nov 2007 11:49:26 -0600 [thread overview]
Message-ID: <472F57A6.3020107@lwfinger.net> (raw)
John,
I did the following set of steps:
git clone --reference ~/linux-2.6 \
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git junk
cd junk
git checkout -b everything origin/everything
git pull
Warning: No merge candidate found because value of config option
"branch.everything.merge" does not match any remote branch fetched.
No changes.
I know that when I get the above warning, my branch "everything" is never updated. My previous
wireless-2.6 tree was stuck at 2.6.23-rc9, whereas "git describe" lists the new tree at
v2.6.24-rc1-155-g792296c.
What am I doing wrong?
Larry
next reply other threads:[~2007-11-05 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 17:49 Larry Finger [this message]
2007-11-05 18:27 ` Problem with wireless-2.6 Luis R. Rodriguez
2007-11-05 18:40 ` Andreas Schwab
[not found] ` <20071105182825.GA3478@tuxdriver.com>
2007-11-05 21:05 ` Larry Finger
2007-11-05 21:17 ` Andreas Schwab
2007-11-06 2:10 ` Pavel Roskin
2007-11-06 3:45 ` Larry Finger
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=472F57A6.3020107@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).