public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.13-rc1
Date: Wed, 29 Jun 2005 02:29:07 -0700	[thread overview]
Message-ID: <20050629092907.GT3334@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0506282310040.14331@ppc970.osdl.org>

On Tue, Jun 28, 2005 at 11:30:54PM -0700, Linus Torvalds wrote:
> Anyway, I really don't want to drag out 2.6.13 as long as 2.6.12 took, and
> we don't have any reason to anyway, so let's try to see if we can calm
> things down again, and people who are thinking about writing new code
> might think about spending some quality time looking at the existing code
> and patches instead.

I would be much obliged if this recommendation were followed, and far
greater care exercised once relaxed.


-- wli

  parent reply	other threads:[~2005-06-29  9:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29  6:30 Linux 2.6.13-rc1 Linus Torvalds
2005-06-29  7:46 ` Brice Goglin
2005-06-29  9:02   ` Brice Goglin
2005-06-29  9:29 ` William Lee Irwin III [this message]
2005-06-29 12:13 ` Linux 2.6.13-rc1 - [PATCH] Don't fill up log with atxp1 vcore change message Prakash Punnoor
2005-06-29 15:01 ` Linux 2.6.13-rc1 - bad tag in git tree? Dave Kleikamp
2005-06-29 15:28   ` Jeff Garzik
2005-06-29 15:45   ` Linus Torvalds
2005-06-29 19:31 ` Linux 2.6.13-rc1 Jesper Juhl
2005-06-29 21:00   ` David Weinehall
2005-06-29 22:34 ` Bill Davidsen
     [not found] <4kEoS-Am-3@gated-at.bofh.it>
2005-06-29 14:23 ` Ronny V. Vindenes
2005-06-29 14:58   ` Tomasz Torcz
2005-06-29 15:07     ` Hugh Dickins
2005-06-29 15:20       ` Ronny V. Vindenes

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=20050629092907.GT3334@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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