From: Jeff Garzik <jeff@garzik.org>
To: Linux IDE mailing list <linux-ide@vger.kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: libata-dev moved to github
Date: Tue, 13 Sep 2011 16:31:38 -0400 [thread overview]
Message-ID: <4E6FBDAA.9010701@garzik.org> (raw)
Since k.org seems to be taking a while, libata-dev.git has moved to
github: git://github.com/jgarzik/libata-dev.git
The branch names remain the same:
NEXT - linux-next branch (hello Stephen, please pull this)
ALL - linux-next + any additional bits we want to test, that are not
quite ready for NEXT. Originally this was created for akpm's -mm tree,
but I'm not sure he pulls this anymore.
upstream - queued for upstream, often equivalent to NEXT
upstream-fixes - fixes queued for upstream. not used when merge window
is open. Typically pushed rapidly to Linus. NOTE: Does not exist yet
at github, but will soon, when I merge a couple fixes later today.
next reply other threads:[~2011-09-13 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 20:31 Jeff Garzik [this message]
2011-09-14 0:28 ` libata-dev moved to github Stephen Rothwell
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=4E6FBDAA.9010701@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.