From: Chris Ball <cjb@laptop.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Theodore Ts'o" <tytso@mit.edu>, Jiri Kosina <trivial@kernel.org>
Subject: Re: [PATCH] Remove drivers/char/ChangeLog
Date: Thu, 18 Feb 2010 13:49:13 -0500 [thread overview]
Message-ID: <m37hqamlau.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <20100218095200.63509b8c@bike.lwn.net> (Jonathan Corbet's message of "Thu, 18 Feb 2010 09:52:00 -0700")
Hi,
> The ChangeLog file under drivers/char is 30K of stuff dedicated
> to the mid-90's TTY exploits of Ted Ts'o; it has been updated
> once since 1998 - and that was in 2001. It's interesting
> history, but we don't normally carry that kind of history inline
> with the code. Let's remove it.
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
Last changed dates:
arch/arm/nwfpe/ChangeLog = 2003/03
drivers/parport/ChangeLog = 2001/10
fs/befs/ChangeLog = 2002/03
fs/ntfs/ChangeLog = 2007/10
The ntfs changelog is modified recently, but the ChangeLog text added
to it is duplicated as the commit message for each change, so those
ChangeLog entries are redundant -- they're already in the commit
history, unless you want changes from earlier than the initial import
cutoff in 2004, in which case you'd need the history repo for those.
- Chris.
--
Chris Ball <cjb@laptop.org>
One Laptop Per Child
next prev parent reply other threads:[~2010-02-18 19:00 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 [this message]
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
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=m37hqamlau.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
--cc=tytso@mit.edu \
/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