From: Gustavo Padovan <gustavo@padovan.org>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Bluetooth trees back to kernel.org
Date: Sat, 8 Oct 2011 03:35:30 -0300 [thread overview]
Message-ID: <20111008063530.GA6767@joana> (raw)
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
Hi Everyone,
Today I got my new credentials from kernel.org and managed to push my trees back
to there. Now you can see both bluetooth-next[1] and bluetooth current[2] at
git.kernel.org
The bluetooth kernel trees hosted at github won't be updated anymore and
shouldn't be considered as upstream.
Also I took the opportunity to extinct bluetooth-next-2.6 and bluetooth-2.6
trees(that were only copies of bluetooth-next and bluetooth trees). These
names doesn't make sense anymore after the 3.0 release.
Regards,
Gustavo
[1] http://git.kernel.org/?p=linux/kernel/git/padovan/bluetooth-next.git
[2] http://git.kernel.org/?p=linux/kernel/git/padovan/bluetooth.git
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2011-10-08 6:35 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=20111008063530.GA6767@joana \
--to=gustavo@padovan.org \
--cc=linux-bluetooth@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).