From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, Steven French <sfrench@us.ibm.com>,
Steven Whitehouse <swhiteho@redhat.com>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
Jeff Garzik <jeff@garzik.org>, Ralf Baechle <ralf@linux-mips.org>,
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: Tue, 13 May 2008 22:33:40 +1000 [thread overview]
Message-ID: <20080513223340.de2bb4a4.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080513124745.24158a93@mjolnir.drzeus.cx>
[-- Attachment #1: Type: text/plain, Size: 501 bytes --]
Hi Pierre,
On Tue, 13 May 2008 12:47:45 +0200 Pierre Ossman <drzeus-list@drzeus.cx> wrote:
>
> That's correct. But I've always made sure that for-linus is the base for
> for-andrew (now next), so that should not be necessary.
What it allows me to do, though, is drop your "next" tree if things go
really bad without dropping fixes for Linus' current tree that you deem
necessary.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-05-13 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080502151206.b40f77ea.akpm@linux-foundation.org>
2008-05-13 6:36 ` git trees which are not yet in linux-next Pierre Ossman
2008-05-13 7:00 ` Stephen Rothwell
2008-05-13 10:47 ` Pierre Ossman
2008-05-13 12:33 ` Stephen Rothwell [this message]
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=20080513223340.de2bb4a4.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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=jeff@garzik.org \
--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 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).