From: Kalle Valo <kvalo@qca.qualcomm.com>
To: <ath6kl-devel@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: ath6kl-next branch rebased
Date: Wed, 24 Oct 2012 17:07:09 +0300 [thread overview]
Message-ID: <87pq480xrm.fsf@qca.qualcomm.com> (raw)
Hi,
I had to rebase ath6kl-next branch in ath6kl.git due to a commit
immediately followed by a revert. Most likely our upstream maintainers
don't like that so I wanted to avoid a publig flogging =)
The downside is that some of the commit ids have changed. But master
branch is unaffected, the users of master branch can still do 'git pull'
and everything will just work. I also updated master branch to
3.7-rc2-wl.
But don't even dream about using bisect on the master branch, the
history on that branch is so ugly that it won't work. For bisect or
checking the git history I recommend to use ath6kl-next branch.
Kalle
reply other threads:[~2012-10-24 14:07 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=87pq480xrm.fsf@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl-devel@qca.qualcomm.com \
--cc=linux-wireless@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).