public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Nelson <james4765@verizon.net>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH 5/5] documentation: Remove drivers/char/README.cycladesZ
Date: Thu, 04 Nov 2004 10:37:36 -0500	[thread overview]
Message-ID: <418A4CC0.3000206@verizon.net> (raw)
In-Reply-To: <20041103214530.GD4716@logos.cnet>

Marcelo Tosatti wrote:
>
>>My unofficial "guidelines" for what needs to be looked at more closely 
>>include: references to 2.0, 2.1, 2.2, 2.3, or 2.5 kernels, references to 
>>external modules, dates of 2002 or earlier, or just a "wait a minute, I 
>>don't think that's right". Not the prettiest technique, I know.
> 
> 
> I think what your intention is good, we dont want obsolete files
> which are not pertinent to v2.6 around - but you need to be careful. 
> 
> Old documents are not necessarily obsolete.
> 
> I would suggest sending all the patches to the respective maintainers,
> removing only the ones which are _obviously_ obsolete (like the CyclomY 
> which talks about upgrading from 2.0 to 2.2).
> 
> README.ecpa and README.scc, which you remove on your patches,
> look valid and useful documentation to me. 
> 

README.ecpa has been unchanged since at least 2.4.18, and the maintainer is no 
longer maintaining it in-kernel for 2.6.  Digi has a maintained version on their 
website.  The document details the user-space programs needed for firmware 
loading, and the version at Digi's website is maintained.

README.scc is fundamentally unchanged since at least 2.2.20.  That's my reason for 
removing it.  The file it points to was also last updated in the 2.2 kernel series 
- I need to get a more complete LXR setup here at home to pin it down more 
accurately.  It's for an AX.25 network adapter, and has no need to be in drivers/char.

> 
>>>Move the rest to Documentation/serial, fine.
> 
> 


      reply	other threads:[~2004-11-04 15:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-03 15:22 [PATCH 1/5] documentation: Remove drivers/char/README.computone james4765
2004-11-03 15:22 ` [PATCH 2/5] documentation: Remove drivers/char/README.cyclomY james4765
2004-11-03 15:23 ` [PATCH 3/5] documentation: Remove drivers/char/README.ecpa james4765
2004-11-03 15:23 ` [PATCH 4/5] documentation: Remove drivers/char/README.scc james4765
2004-11-03 15:23 ` [PATCH 5/5] documentation: Remove drivers/char/README.cycladesZ james4765
2004-11-03 13:31   ` Marcelo Tosatti
2004-11-03 17:52     ` Jim Nelson
2004-11-03 15:09       ` Marcelo Tosatti
2004-11-03 22:04         ` Jim Nelson
2004-11-03 21:45           ` Marcelo Tosatti
2004-11-04 15:37             ` Jim Nelson [this message]

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=418A4CC0.3000206@verizon.net \
    --to=james4765@verizon.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    /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