From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>
Subject: Re: linux-next: first tree
Date: Thu, 14 Feb 2008 16:25:09 +0100 [thread overview]
Message-ID: <1203002709.1044.5.camel@localhost> (raw)
In-Reply-To: <20080215020019.f7cb5895.sfr@canb.auug.org.au>
On Fri, 2008-02-15 at 02:00 +1100, Stephen Rothwell wrote:
> I would prefer that the trees be added by the subsystem maintainers and
> they can tell me which branch represents their expectations for the next
> kernel release (in this case 2.6.26). But thanks, hopefully you will have
> prodded them along. :-)
For the s390 architecture please use the "features" branch of git390:
git://git390.osdl.marist.edu/pub/scm/linux-2.6.git features
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2008-02-14 15:25 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 13:35 linux-next: first tree Stephen Rothwell
2008-02-14 14:06 ` Jiri Kosina
2008-02-14 14:34 ` Stephen Rothwell
2008-02-14 14:45 ` Rafael J. Wysocki
2008-02-14 15:00 ` Stephen Rothwell
2008-02-14 15:25 ` Martin Schwidefsky [this message]
2008-02-14 21:48 ` Stephen Rothwell
2008-02-14 15:49 ` Paul Mundt
2008-02-14 21:58 ` Stephen Rothwell
2008-02-14 15:54 ` Dave Kleikamp
2008-02-14 22:01 ` Stephen Rothwell
2008-02-15 4:58 ` Len Brown
2008-02-15 6:19 ` Stephen Rothwell
2008-02-14 16:04 ` Andy Whitcroft
2008-02-20 14:23 ` Stephen Rothwell
2008-02-20 16:47 ` Randy Dunlap
2008-02-22 0:07 ` Frank Seidel
2008-02-22 0:12 ` Randy Dunlap
2008-02-22 0:22 ` Harvey Harrison
2008-02-22 5:31 ` Frank Seidel
2008-02-22 0:15 ` Greg KH
2008-02-22 5:33 ` Frank Seidel
2008-02-22 0:28 ` Stephen Rothwell
2008-02-22 5:41 ` Frank Seidel
2008-02-22 5:55 ` Stephen Rothwell
2008-02-14 17:38 ` Mauro Carvalho Chehab
2008-02-14 22:24 ` Stephen Rothwell
2008-02-18 16:07 ` Mauro Carvalho Chehab
2008-02-14 18:29 ` Yinghai Lu
2008-02-14 18:39 ` Benny Halevy
2008-02-14 20:20 ` Greg KH
2008-02-14 20:50 ` Sam Ravnborg
2008-02-14 23:52 ` Stephen Rothwell
2008-02-14 23:31 ` Stephen Rothwell
2008-02-14 20:23 ` Sam Ravnborg
2008-02-14 23:35 ` Stephen Rothwell
2008-02-14 21:03 ` Jeff Garzik
2008-02-14 21:05 ` Jeff Garzik
2008-02-14 21:26 ` James Bottomley
2008-02-14 21:45 ` Jeff Garzik
2008-02-14 23:58 ` Stephen Rothwell
2008-02-14 22:27 ` Trond Myklebust
2008-02-15 0:33 ` Stephen Rothwell
2008-02-15 21:00 ` J. Bruce Fields
2008-02-16 15:37 ` Stephen Rothwell
2008-02-14 23:17 ` David Chinner
2008-02-15 0:50 ` Stephen Rothwell
2008-02-15 1:10 ` David Chinner
2008-02-15 2:14 ` Stephen Rothwell
2008-02-15 8:33 ` Bryan Wu
2008-02-16 15:33 ` Stephen Rothwell
2008-02-17 2:23 ` Robin Getz
2008-02-17 5:33 ` Stephen Rothwell
2008-02-16 15:13 ` Stefan Richter
2008-02-16 15:40 ` Stephen Rothwell
2008-02-17 19:09 ` Mark M. Hoffman
2008-02-17 23:27 ` Stephen Rothwell
2008-02-18 8:04 ` Artem Bityutskiy
2008-02-18 8:29 ` Stephen Rothwell
2008-02-18 11:11 ` Paolo Ciarrocchi
2008-02-18 13:15 ` 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=1203002709.1044.5.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rjw@sisk.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox