mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Shane <gnome42@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: WTF does -rc mean? was [PATCH] x86, tsc: fix section mismatch warning
Date: Mon, 18 Aug 2008 15:30:50 +1000	[thread overview]
Message-ID: <200808181530.50995.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <fa4052ef0808172003r48863a4fu90c0647eef736571@mail.gmail.com>

On Monday 18 August 2008 13:03, Shane wrote:

> This is the third** -rc cycle where I have composed what is meant to
> be a scorching
> email to the kernel list about the mind blowing decline in -rc kernel
> developer attitude.
> I didn't send the other two but I just spent another two flippin'
> hours booting and
> fsck'in. And I am very cranky  (to put it politely) because the
> bleep'n problem is known
> and the fix has been available for at least 7 days!!
>
> I of course understand that there will be bugs in the -rc kernels,
> that is why I bother putting
> the time and energy into testing them.  It is mainly the lackadaisical
> attitude about getting
> the fixes in that is a mind blower.
>
> I am a (fairly long time) tester/luser of the kernel. I do it for fun
> and to learn.
> It isn't fun anymore.

It stands for "ridiculous count". I'm not joking.

If you want something approaching a "release candidate", you have to
use the last one or two -rcN releases before the final release. This
obviously requires guesswork.

      reply	other threads:[~2008-08-18  5:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18  3:03 Shane
2008-08-18  5:30 ` Nick Piggin [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=200808181530.50995.nickpiggin@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=gnome42@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®