linux-kernel - Re: [PATCH] blackfin/sram: use 'unsigned long' for irqflags

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: <Pine.LNX.4.64.0808061417540.20424@pc-004.diku.dk>
Date:	Wed, 6 Aug 2008 14:21:17 +0200 (CEST)
From:	Julia Lawall <julia@...u.dk>
To:	Mike Frysinger <vapier.adi@...il.com>
Cc:	Vegard Nossum <vegard.nossum@...il.com>,
	Bryan Wu <cooloney@...nel.org>,
	Alexey Dobriyan <adobriyan@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] blackfin/sram: use 'unsigned long' for irqflags

> *shrug* ... i dont see other patches with things like:
> The patch was generated with git.
> The patch was generated with eclipse.
> The patch was generated with emacs.
> etc...
> 
> we dont generally list all of the tools in the log message that was
> used in *creating* a patch since it doesnt really add any value when
> looking back historically at changes.

But with git, emacs, eclipse etc, the person is still making the change by 
hand.  The comment is more like "this patch was generated with perl" or 
"this patch was generated with sed", indicating that the change is 
uniform enough to be automated.  This does have some interest, 
although perhaps not for everyone.

julia
--
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/