linux-kernel - Re: [PATCH] Remove drivers/char/ChangeLog

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LNX.2.00.1002182300520.30967@pobox.suse.cz>
Date:	Thu, 18 Feb 2010 23:02:33 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Chris Ball <cjb@...top.org>
Cc:	Jonathan Corbet <corbet@....net>,
	LKML <linux-kernel@...r.kernel.org>,
	Theodore Ts'o <tytso@....edu>
Subject: Re: [PATCH] Remove drivers/char/ChangeLog

On Thu, 18 Feb 2010, Chris Ball wrote:

>    > 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.

I think we could nuke them all, but I'd suggest first checking with 
maintainers of the code in question. It's possible that they do some kind 
of auto-import from some weird external repositories in which they 
auto-generate this Changelog file, so they might re-appear later (not 
everyone is using git even these days ... strange, but apparently true).

Thanks,

-- 
Jiri Kosina
SUSE Labs, Novell Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/