public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Pezoa <dpforos@yahoo.com>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: kernel <linux-kernel@vger.kernel.org>
Subject: Re: patches question
Date: Wed, 20 Aug 2003 08:59:56 -0700 (PDT)	[thread overview]
Message-ID: <20030820155956.67452.qmail@web11201.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0308191339430.1464-100000@coffee.psychology.mcmaster.ca>


--- Mark Hahn <hahn@physics.mcmaster.ca> wrote:
> > success, in order to know the list purposes. But i
> > think questions about: kernel, kernel modules and
> > drivers should be ok.
> 
> the point is that it's simply inappropriate to ask
> questions that you can easily answer yourself.

I think what is easy and what not is relative, if you
are more documented about kernel and use english as
your primary language, many question appear to you as
basic.

I think my question appear to you easy. I know your
answer after you make it. That is because the question
is not all specific it should be. But i think the
answers i get should be more completes. Example:

your response:

ac = alan cox

expected response:

ac is Alan Cox and this patches are oriented to
support x hardware..., (i don't found it in the faq,
may be because alan cox patches only solve problems
aleatory, without one specific purpose, and that is
the only answer i can get to my question), and the
documentation for alan cox patches are in that url
.... that link should be usefull too
http://www.linuxhq.com/lkprogram.html

> 
> > Otherwise the list must be
> > called kernel-bugs-report or mark-hahn-kernel-bugs
> :-)
> > or something similar
> 
> the list is specifically "discussion of
> kernel-development issues".
> it's not "how do I find the most introductory
> information possible".
> for instance, patches are almost certainly
> well-described in the 
> lkml faq, and changelogs are found in the most
> logical possible
> place (www.kernel.org).

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.

> 
> lkml is not a kernel-bug list, nor do I have any
> importance to it.
> I simply offered you some advice out of charity.
>

If one question is easy to answer it not make it not
important, is important for who make it, not for you.
If exist other list, forum, ... more related to kernel
 and kernel patched and it's drivers compilation
problems please let me know it.

If i make more questions in that list, i will make
more specific questions in order to get more usefull
answers. But probably not because i think that list is
only for who develop the kernel and not for who
compile and use them and it's patches and drivers.

Thanks for your help and Good luck!!

Daniel Pezoa


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

       reply	other threads:[~2003-08-20 16:00 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 ` Daniel Pezoa [this message]
2003-08-20 16:33   ` patches question Randy.Dunlap
2003-08-24  5:11     ` Rob Landley
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=20030820155956.67452.qmail@web11201.mail.yahoo.com \
    --to=dpforos@yahoo.com \
    --cc=hahn@physics.mcmaster.ca \
    --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