All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for July 29
Date: Tue, 29 Jul 2008 16:45:58 +0200	[thread overview]
Message-ID: <20080729144558.GC32430@isilmar.linta.de> (raw)
In-Reply-To: <20080729172337.b3d74100.sfr@canb.auug.org.au>

Hi,

On Tue, Jul 29, 2008 at 05:23:37PM +1000, Stephen Rothwell wrote:
> Changes since next-20080728:

is linux-next now open for 2.6.28 stuff?

Thanks,
	Dominik

  parent reply	other threads:[~2008-07-29 14:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29  7:23 linux-next: Tree for July 29 Stephen Rothwell
2008-07-29  7:48 ` Fernando Luis Vázquez Cao
2008-07-29 14:45 ` Dominik Brodowski [this message]
2008-08-03 14:56   ` Stephen Rothwell
2008-08-04  7:58     ` Dominik Brodowski
2008-07-29 16:25 ` Bartlomiej Zolnierkiewicz
2008-07-29 18:16   ` Greg KH
2008-07-29 20:49     ` Hugh Dickins
2008-07-30  4:48       ` Greg KH
2008-07-30  7:06         ` Bernhard Walle
2008-07-30  9:19           ` Andrew Morton
2008-07-30 19:27             ` Bartlomiej Zolnierkiewicz
2008-07-30 20:04               ` Andrew Morton
2008-07-30 23:41                 ` Stephen Rothwell
2008-07-30 23:44                   ` Greg KH
2008-08-07  1:08                     ` Stephen Rothwell
2008-08-07  3:40                       ` Greg KH
2008-08-07  6:10                         ` Stephen Rothwell
2008-07-30  1:05   ` linux-next: usb tree fix (Was: Re: linux-next: Tree for July 29) Stephen Rothwell
2008-07-30 19:38     ` Bartlomiej Zolnierkiewicz
  -- strict thread matches above, loose matches on Subject: below --
2009-07-29  7:36 linux-next: Tree for July 29 Stephen Rothwell
2010-07-29  4:32 Stephen Rothwell
2011-07-29  7:38 Stephen Rothwell
2011-07-30 11:38 ` Sedat Dilek
2011-07-30 16:08   ` Arnaud Lacombe
2011-07-30 16:16     ` Sedat Dilek

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=20080729144558.GC32430@isilmar.linta.de \
    --to=linux@dominikbrodowski.net \
    --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.