From: Russ Dill <Russ.Dill@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Remove drivers/char/ChangeLog
Date: Fri, 19 Feb 2010 06:06:26 +0000 (UTC) [thread overview]
Message-ID: <loom.20100219T063902-409@post.gmane.org> (raw)
In-Reply-To: m37hqamlau.fsf@pullcord.laptop.org
> Should we lose the others too, then?
>
> pullcord:cjb~/git/linux-2.6 % du -sh **/ChangeLog
> 8.0K arch/arm/nwfpe/ChangeLog
> 32K drivers/char/ChangeLog
> 20K drivers/parport/ChangeLog
> 16K fs/befs/ChangeLog
> 100K fs/ntfs/ChangeLog
>
There are several others scattered around
Archives of changelogs
16K Documentation/ide/ChangeLog.ide-cd.1994-2004
4.0K Documentation/ide/ChangeLog.ide-floppy.1996-2002
16K Documentation/ide/ChangeLog.ide-tape.1995-2002
64K Documentation/scsi/ChangeLog.1992-1997
Last updated in 1997!
14K sound/oss/CHANGELOG
Updated periodically by Nick Cheng <nick.cheng@areca.com.tw>
8.0K Documentation/scsi/ChangeLog.arcmsr
Updated periodically by various LSI employees
24K Documentation/scsi/ChangeLog.megaraid
16K Documentation/scsi/ChangeLog.megaraid_sas
Added with driver in 2005, never updated
92K Documentation/scsi/ChangeLog.lpfc
Last updated 2002
8.0K Documentation/scsi/ChangeLog.ips
24K Documentation/scsi/ChangeLog.ncr53c8xx
32K Documentation/scsi/ChangeLog.sym53c8xx
8.0K Documentation/scsi/ChangeLog.sym53c8xx_2
But of course, there are changelogs in all sorts of other files as well, along
with severely outdated TODOs (such as Documentation/kernel-parameters.txt circa
2002)
prev parent reply other threads:[~2010-02-19 6:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 16:52 [PATCH] Remove drivers/char/ChangeLog Jonathan Corbet
2010-02-18 18:03 ` Alan Cox
2010-02-18 18:17 ` tytso
2010-02-18 22:00 ` Jiri Kosina
2010-02-18 18:49 ` Chris Ball
2010-02-18 22:02 ` Jiri Kosina
2010-02-18 23:37 ` Alan Cox
2010-02-18 23:43 ` Jiri Kosina
2010-02-19 6:06 ` Russ Dill [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=loom.20100219T063902-409@post.gmane.org \
--to=russ.dill@gmail.com \
--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