From: Jeff Garzik <jeff@garzik.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Feb 27
Date: Wed, 27 Feb 2008 12:30:59 -0500 [thread overview]
Message-ID: <47C59E53.4080701@garzik.org> (raw)
In-Reply-To: <20080228010626.fd4e00d2.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> But on the plus side I also have:
>
> libata-dev (same as git-libata-all?)
Intentionally different. libata-dev.git#NEXT is for linux-next, and
libata-dev.git#ALL is for -mm.
Jeff
next prev parent reply other threads:[~2008-02-27 17:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 6:03 linux-next: Tree for Feb 27 Stephen Rothwell
2008-02-27 6:09 ` Stephen Rothwell
2008-02-27 7:00 ` Andrew Morton
2008-02-27 14:06 ` Stephen Rothwell
2008-02-27 14:43 ` Paul Moore
2008-02-27 15:31 ` Stephen Rothwell
2008-02-27 16:06 ` Paul Moore
2008-02-27 17:30 ` Jeff Garzik [this message]
2008-02-27 22:54 ` Stephen Rothwell
2008-02-27 19:55 ` Theodore Tso
2008-02-27 23:06 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2012-02-27 7:20 Stephen Rothwell
2013-02-27 2:44 Stephen Rothwell
2013-02-27 2:44 ` Stephen Rothwell
2014-02-27 6:03 Stephen Rothwell
2014-02-27 6:03 ` Stephen Rothwell
2015-02-27 4:49 Stephen Rothwell
2017-02-27 3:34 Stephen Rothwell
2018-02-27 4:03 Stephen Rothwell
2019-02-27 6:44 Stephen Rothwell
2020-02-27 4:22 Stephen Rothwell
2023-02-27 1:18 Stephen Rothwell
2024-02-27 6:04 Stephen Rothwell
2025-02-27 7:25 Stephen Rothwell
2026-02-27 14:50 Mark Brown
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=47C59E53.4080701@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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.