All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: mkrufky@m1k.net
Cc: Bodo Eggert <7eggert@gmx.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	Sean Bruno <sean.bruno@dsl-only.net>,
	Lee Revell <rlrevell@joe-job.com>,
	webmaster@kernel.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Testing RC kernels [KORG]
Date: Tue, 02 Aug 2005 21:57:23 -0700	[thread overview]
Message-ID: <42F04EB3.6040007@zytor.com> (raw)
In-Reply-To: <42F048B5.8030000@m1k.net>

Michael Krufky wrote:
> 
> Why not just have the scripts plug values into a database, and have the 
> html/php be formatted like Bodo suggests, and reads content from database?
> Very simple, less maintenance... Only requires 1 initial redesign, and 
> easier maintainence of the scripts that you speak of.
> 

The issue is to generate the values, not present them.

	-hpa

  reply	other threads:[~2005-08-03  4:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03  0:41 Testing RC kernels [KORG] Bodo Eggert
2005-08-03  4:21 ` H. Peter Anvin
2005-08-03  4:31   ` Michael Krufky
2005-08-03  4:57     ` H. Peter Anvin [this message]
2005-08-03 19:48       ` Bodo Eggert
  -- strict thread matches above, loose matches on Subject: below --
2005-08-03  0:00 Shayne O'Connor
2005-08-02 18:33 Testing RC kernels Sean Bruno
2005-08-02 18:36 ` Lee Revell
2005-08-02 18:36   ` Sean Bruno
2005-08-02 18:54     ` Lee Revell
2005-08-02 19:21       ` Testing RC kernels [KORG] Steven Rostedt
2005-08-02 21:05         ` Sean Bruno
2005-08-02 21:27           ` Michael Krufky
2005-08-03  2:04         ` Gene Heskett
2005-08-03  2:13           ` Randy.Dunlap
2005-08-03  2:35             ` Steven Rostedt
2005-08-03  3:30             ` Gene Heskett
2005-08-03 21:52               ` Andrew James Wade
2005-08-04  0:02                 ` John Stoffel

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=42F04EB3.6040007@zytor.com \
    --to=hpa@zytor.com \
    --cc=7eggert@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkrufky@m1k.net \
    --cc=rlrevell@joe-job.com \
    --cc=rostedt@goodmis.org \
    --cc=sean.bruno@dsl-only.net \
    --cc=webmaster@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 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.