From: Jeff Garzik <jeff@garzik.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-next@vger.kernel.org, Steven French <sfrench@us.ibm.com>,
Steven Whitehouse <swhiteho@redhat.com>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
Ralf Baechle <ralf@linux-mips.org>,
Pierre Ossman <drzeus-list@drzeus.cx>, Jan Kara <jack@ucw.cz>,
Anton Vorontsov <cbou@mail.ru>,
Jens Axboe <jens.axboe@oracle.com>,
Eric Van Hensbergen <ericvh@gmail.com>,
Wim Van Sebroeck <wim@iguana.be>,
Christian Zankel <chris@zankel.net>, Nicolas Pitre <nico@cam.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <clameter@sgi.com>,
Erez Zadok <ezk@cs.sunysb.edu>,
linux-kernel@vger.kernel.org
Subject: Re: git trees which are not yet in linux-next
Date: Fri, 02 May 2008 18:20:26 -0400 [thread overview]
Message-ID: <481B93AA.7040000@garzik.org> (raw)
In-Reply-To: <20080502151206.b40f77ea.akpm@linux-foundation.org>
Andrew Morton wrote:
> (Jeff, git-libata-all is a pretty important one)
libata-dev.git#NEXT is for linux-next, and libata-dev.git#ALL is for -mm
Already taken care of.
Jeff
next prev parent reply other threads:[~2008-05-02 22:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 22:12 git trees which are not yet in linux-next Andrew Morton
2008-05-02 22:20 ` Jeff Garzik [this message]
2008-05-02 22:33 ` Andrew Morton
2008-05-03 4:33 ` Stephen Rothwell
2008-05-03 4:54 ` Jeff Garzik
2008-05-02 22:42 ` Andrew Morton
2008-05-03 1:19 ` Stefan Richter
2008-05-03 1:34 ` Andrew Morton
2008-05-03 4:52 ` Jeff Garzik
2008-05-03 8:46 ` Stefan Richter
2008-05-05 0:18 ` Stephen Rothwell
2008-05-03 1:11 ` Stefan Richter
2008-05-03 1:18 ` Andrew Morton
2008-05-05 16:52 ` Liam Girdwood
2008-05-05 17:57 ` Andrew Morton
2008-05-06 4:45 ` Stephen Rothwell
2008-05-06 5:50 ` Andrew Morton
2008-05-06 7:18 ` Stephen Rothwell
2008-05-05 18:16 ` Pekka Enberg
2008-05-05 18:31 ` Andrew Morton
2008-05-05 18:41 ` Pekka J Enberg
2008-05-05 19:40 ` Stefan Richter
2008-05-05 21:11 ` Daniel Hazelton
2008-05-06 4:41 ` Stephen Rothwell
2008-05-06 4:43 ` Stephen Rothwell
2008-05-13 6:36 ` Pierre Ossman
2008-05-13 7:00 ` Stephen Rothwell
2008-05-13 10:47 ` Pierre Ossman
2008-05-13 12:33 ` Stephen Rothwell
2008-10-02 9:42 ` Wim Van Sebroeck
2008-10-13 6:30 ` 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=481B93AA.7040000@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=cbou@mail.ru \
--cc=chris@zankel.net \
--cc=clameter@sgi.com \
--cc=drzeus-list@drzeus.cx \
--cc=ericvh@gmail.com \
--cc=ezk@cs.sunysb.edu \
--cc=jack@ucw.cz \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nico@cam.org \
--cc=penberg@cs.helsinki.fi \
--cc=ralf@linux-mips.org \
--cc=sfrench@us.ibm.com \
--cc=stefanr@s5r6.in-berlin.de \
--cc=swhiteho@redhat.com \
--cc=wim@iguana.be \
/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.