mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "John Stoffel" <john@stoffel.org>
To: andrew.j.wade@gmail.com
Cc: Gene Heskett <gene.heskett@verizon.net>,
	linux-kernel@vger.kernel.org, webmaster@kernel.org
Subject: Re: Testing RC kernels [KORG]
Date: Wed, 3 Aug 2005 20:02:33 -0400	[thread overview]
Message-ID: <17137.23321.832718.662521@smtp.charter.net> (raw)
In-Reply-To: <200508031753.00402.andrew.j.wade@gmail.com>

>>>>> "Andrew" == Andrew James Wade <andrew.j.wade@gmail.com> writes:

Andrew> I updated my kernel more frequently after learning of ketchup.
Andrew> (<http://www.selenic.com/ketchup/>). The bother of getting the
Andrew> patch sequence right and applying it was enough to discourage me.
Andrew> No, it's not particularly difficult, but it may well be enough
Andrew> to discourage casual testers. 

Hear hear!  Ketchup is an amazing tool and automates a boring task, so
it's got my vote for most useful kernel build tool right now.

John

  reply	other threads:[~2005-08-04  0:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2005-08-02 18:37 ` Testing RC kernels Michael Krufky
2005-08-03 10:52   ` Jiri Slaby
2005-08-03  0:00 Testing RC kernels [KORG] Shayne O'Connor
2005-08-03  0:41 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
2005-08-03 19:48       ` Bodo Eggert

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=17137.23321.832718.662521@smtp.charter.net \
    --to=john@stoffel.org \
    --cc=andrew.j.wade@gmail.com \
    --cc=gene.heskett@verizon.net \
    --cc=linux-kernel@vger.kernel.org \
    --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 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®