public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: "Randy.Dunlap" <rddunlap@osdl.org>, Daniel Pezoa <dpforos@yahoo.com>
Cc: hahn@physics.mcmaster.ca, linux-kernel@vger.kernel.org
Subject: Re: patches question
Date: Sun, 24 Aug 2003 01:11:58 -0400	[thread overview]
Message-ID: <200308240111.58758.rob@landley.net> (raw)
In-Reply-To: <20030820093347.4f024a89.rddunlap@osdl.org>

On Wednesday 20 August 2003 12:33, Randy.Dunlap wrote:
> On Wed, 20 Aug 2003 08:59:56 -0700 (PDT) Daniel Pezoa <dpforos@yahoo.com> 
wrote:
> | sorry but i think the faq is incomplete, i think
> | useless for what i need too. It have incomplete
> | answers  and not links references for many important
> | questions. May be should exist one list or forum
> | dedicated to: Kernel, Kernel Patches, Kernel Modules,
> | Kernel Drives and other about Kernel Development and
> | Bugs Report.
>
> The LKML FAQ hasn't been updated since:
> "Last updated on 21 Nov 2002 by Richard Gooch.
> This document is GPL'ed by its various contributors."
>
> and Richard hasn't been heard from lately AFAIK.
>
> I would have just guessed that the FAQ needs some updates...
> Doesn't someone out there want a job?

I've been meaning to give the FAQ a thorough going over for a while now.  
(Bits of it are a lot more stale than 2002.)

I sent Richard a FAQ patch a month ago, which he hasn't responded to, but he 
claims to still be active:

> > Okay, that link needs to go in the "basic linux kernel
> > documentation" section at the start of the
> > "http://www.tux.org/lkml/" faq, along with some other resources that
> > have fallen through the cracks.  I'd happily generate a patch
> > against the FAQ, but haven't a clue what the source format is.  (Is
> > it hand-hacked HTML?)
>
> Yes. A plain uni-diff against the HTML will be fine. I'm busy these
> days, so don't expect a quick response. But I will get around to it.
>
>                               Regards,
>
>                                       Richard....

I sent him the patch in question on July 17th, but haven't heard anything 
back.  (I've been a bit out of touch in the past month myself getting back 
into grad school, buying a condo, moving, etc, and haven't followed up yet.)

If Richard doesn't have time to do it anymore, and there are patches backing 
up, I could give it a whack.  I'm not exactly dripping with free time myself 
at the moment, but I usually catch up with all the important pending things 
at least once a week.  However, I don't want to usurp anybody's 
maintainership.  (I was planning on possibly making my own tree and then 
feeding him incremental patches at whatever rate he responds...)

Rob



  reply	other threads:[~2003-08-25  3:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0308191339430.1464-100000@coffee.psychology.mcmaster.ca>
2003-08-20 15:59 ` patches question Daniel Pezoa
2003-08-20 16:33   ` Randy.Dunlap
2003-08-24  5:11     ` Rob Landley [this message]
2003-08-24  5:16     ` Rob Landley
2003-08-20 16:58 John Bradford
  -- strict thread matches above, loose matches on Subject: below --
2003-08-18 23:25 Daniel Pezoa
2003-08-18 23:34 ` Herbert Pötzl

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=200308240111.58758.rob@landley.net \
    --to=rob@landley.net \
    --cc=dpforos@yahoo.com \
    --cc=hahn@physics.mcmaster.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@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