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: <48148D82.3050204@s5r6.in-berlin.de>
Date:	Sun, 27 Apr 2008 16:28:18 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Richard Purdie <rpurdie@...ys.net>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Adrian Bunk <bunk@...nel.org>,
	Harvey Harrison <harvey.harrison@...il.com>,
	Mauro Carvalho Chehab <mchehab@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: If you want me to quit I will quit

Richard Purdie wrote:
> Its worth realising that these fix patches contain useful information
> too, e.g. they might be by different authors and its also interesting in
> some senses to see what fixes were applied to the original patch, why
> etc. since it is history and that is what the SCM effectively stores.

Important things can be noted in the patch description.  We can also 
refer to mailinglist archives and bug trackers in the patch description.

Caveats:  Changing the patch description means changing the patch 
identity (which different SCMs treat with different rigor).  Also, a 
number of SCM tools assume that there is exactly one author of a patch. 
(Workaround:  Track coauthors informally in the patch description.)

...
> On the other hand I agree that the patches in -mm often have stupid
> typos etc which aren't interesting in the history but where do you draw
> the line?

Indeed.  It's the question of when do I release what to whom.
-- 
Stefan Richter
-=====-==--- -=-- ==-==
http://arcgraph.de/sr/
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ