All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>, Dave Jones <davej@redhat.com>,
	Linus Torvalds <torvalds@osdl.org>
Subject: [PATCH] Clarify -rc definition in Documentation/feature-list-2.6.txt
Date: Fri, 01 Apr 2005 08:31:20 -0700	[thread overview]
Message-ID: <424D6948.4000500@mesatop.com> (raw)

Gentlehackers,

The day to clarify the real definition of "-rc" is finally here.

Steven

--- linux-2.6.12-rc1-mm4/Documentation/feature-list-2.6.txt.orig        2005-04-01 07:56:23.000000000 -0700
+++ linux-2.6.12-rc1-mm4/Documentation/feature-list-2.6.txt     2005-04-01 07:59:21.000000000 -0700
@@ -23,16 +23,21 @@
  Applying patches.
  ~~~~~~~~~~~~~~~~~
  - In 2.4 and previous kernels, the recommended way to apply patches was
    to use a command line such as ...
    gzip -cd patchXX.gz | patch -p0
    In 2.6, Linus started adding an extra path element to the diffs,
    so using -p1 in the untarred 'to be patched' directory is necessary.

+Release Candidates
+~~~~~~~~~~~~~~~~~
+- In 2.4 and previous kernels, -rc meant "release candidate".
+  In 2.6, -rc means "really churning", so even more testing is desired.
+
  Known gotchas.
  ~~~~~~~~~~~~~~
  Certain known bugs are being reported over and over. Here are the
  workarounds.
  - Blank screen after decompressing kernel?
    Make sure your .config has
     CONFIG_INPUT=y
     CONFIG_VT=y

                 reply	other threads:[~2005-04-01 15:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=424D6948.4000500@mesatop.com \
    --to=elenstev@mesatop.com \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.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 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.