public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: sfr@canb.auug.org.au
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for March 19
Date: Thu, 18 Mar 2010 22:07:12 -0700 (PDT)	[thread overview]
Message-ID: <20100318.220712.212678037.davem@davemloft.net> (raw)
In-Reply-To: <20100319160030.a71cd836.sfr@canb.auug.org.au>

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 19 Mar 2010 16:00:30 +1100

> The net tree still has its build failures for which I reverted 3 commits.

Sorry, I must have just missed your pull for today.

net-next-2.6 should have everything sorted now.

  reply	other threads:[~2010-03-19  5:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19  5:00 linux-next: Tree for March 19 Stephen Rothwell
2010-03-19  5:07 ` David Miller [this message]
2010-03-19 10:36   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2009-03-19 11:10 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=20100318.220712.212678037.davem@davemloft.net \
    --to=davem@davemloft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox