linux-kernel - NAK nettiquete (was Re: "Re: [PATCH 0/2] Colored kernel output (run2)"

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: <2614.1191766530@turing-police.cc.vt.edu>
Date:	Sun, 07 Oct 2007 10:15:30 -0400
From:	Valdis.Kletnieks@...edu
To:	Oleg Verych <olecom@...wer.upol.cz>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Jan Engelhardt <jengelh@...putergmbh.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Dave Jones <davej@...hat.com>,
	Krzysztof Halasa <khc@...waw.pl>,
	Medve Emilian-EMMEDVE1 <Emilian.Medve@...escale.com>,
	Helge Deller <deller@....de>
Subject: NAK nettiquete (was Re: "Re: [PATCH 0/2] Colored kernel output (run2)" 

On Sun, 07 Oct 2007 13:10:35 +0200, Oleg Verych said:

> > > I added comment (like this), so anyone can skip reading body, if 
> > > headers are "Oleg Verych && NAK". In case if `NAK' have a magic 
> > > meaning in the LKML, like control characters in the tty, i'm sorry.
> > 
> > yes, a 'NAK' has a particular meaning on lkml.
> 
> But what about (NAK && ! any_important_kernel_developer_name)?

The few times I've tried to NAK something outright, I've always tried to attach
plenty of technical explanation (usually of the form "Gaak, this oopses my
laptop") :), and cc: the relevant important_name, and hope they listen.

Fortunately, most of the time I can get away with a politely phrased variation of
"important_name would probably appreciate if you fixed XYZ and resubmitted"
comment.. ;)

Content of type "application/pgp-signature" skipped