linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Piotr Hosowicz <piotr@hosowicz.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.36-rc3
Date: Mon, 30 Aug 2010 21:28:17 +0200	[thread overview]
Message-ID: <4C7C0651.6070109@example.com> (raw)
In-Reply-To: <AANLkTinRRiW1VUzS+3T82=q8PsoRn78Cgn_X8gSduM0U@mail.gmail.com>

On 29.08.2010 19:25, Linus Torvalds wrote:
> You all know the drill by now: another week, another -rc.
>
> Nothing in particular stands out that I can recall. As usual, it's
> mostly driver updates (65%), of which a large piece (by line count) is
> just the removal of a staging driver that isn't really ready nor
> making any progress. But on the "somewhat more likely to cause
> excitement" front, there's some radeon/nouveau drm updates too.
>
> Outside of drivers, you have CIFS, ceph and xfs filesystem updates,
> and sparc/blackfin on the arch side. And various random noise -
> networking, fsnotify, an anonvma locking fix etc. The appended
> shortlog gives a fairly good idea of what kinds of things have been
> going on.
>
> Anyway, I'm hoping it is going to be an extremely boring -rc, because
> I'm just about to leave for LinuxCon Brazil, and while I'll follow
> issues over email, I'm not planning to do any pulls for the next week.

Will someone tak care of frequent git updates for kernel?

Regards,

Piotr Hosowicz

-- 
Janusz Korwin-Mikke:
"Idiota z dyplomem to taki sam idiota,
jak przedtem - tylko z pretensjami."
NP: Ozzy Osbourne - Mr Tinkertrain
NB: 2.6.36-rc3-20100830-1743+

      parent reply	other threads:[~2010-08-30 19:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-29 17:25 Linux 2.6.36-rc3 Linus Torvalds
2010-08-29 19:24 ` Chris Ball
2010-08-29 19:24 ` Torsten Kaiser
2010-08-29 22:27   ` Yinghai Lu
2010-08-29 22:36     ` Yinghai Lu
2010-08-29 22:53   ` Yinghai Lu
2010-08-30  4:50     ` Torsten Kaiser
2010-08-30  1:12   ` [PATCH] x86, setup: fix earlyprintk=serial,ttyS0,115200 Yinghai Lu
2010-08-30  1:13     ` [PATCH] x86, setup: fix earlyprintk=serial,0x3f8,115200 Yinghai Lu
2010-09-08 21:28       ` H. Peter Anvin
2010-09-09  7:23         ` Yinghai Lu
2010-09-21 19:58       ` [tip:x86/urgent] x86, setup: Fix earlyprintk=serial,0x3f8,115200 tip-bot for Yinghai Lu
2010-09-21 19:58     ` [tip:x86/urgent] x86, setup: Fix earlyprintk=serial,ttyS0,115200 tip-bot for Yinghai Lu
2010-09-22 15:12       ` Early console confusion Bjorn Helgaas
2010-09-22 15:56         ` H. Peter Anvin
2010-09-22 16:44           ` Bjorn Helgaas
2010-09-22 16:53             ` H. Peter Anvin
2010-09-22 18:21               ` Bjorn Helgaas
2010-09-22 18:26                 ` H. Peter Anvin
2010-08-29 22:40 ` Linux 2.6.36-rc3 Jean-Denis Girard
2010-08-30  5:23   ` Borislav Petkov
2010-08-30  8:00     ` Jean-Denis Girard
2010-08-30  8:47 ` Miguel Calleja
2010-08-30 17:00   ` Suresh Jayaraman
2010-08-30 17:14     ` Shirish Pargaonkar
2010-08-30 17:25       ` Randy Dunlap
2010-08-30 21:27         ` Steve French
2010-08-30 19:28 ` Piotr Hosowicz [this message]

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=4C7C0651.6070109@example.com \
    --to=piotr@hosowicz.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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).