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] [day] [month] [year] [list]
Date:	Mon, 04 Aug 2008 17:11:23 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Ben Dooks <ben-linux@...ff.org>,
	James Bottomley <James.Bottomley@...senPartnership.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-scsi <linux-scsi@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PATCH] SCSI fixes for 2.6.27-rc1

Alan Cox wrote:
>> I thought group (or non-person) submissions where explicitly
>> prohibitted in the signoff section in Documentation/SubmittingPatches
> 
> Highpoint is a legal entity so highpoint can enter into agreements. Thats
> a bit different from say "Dave the anonymous ferret" or "three people
> down the pub"
> 
> In many ways companies that sign the patches themselves are being nicer
> to their employees than those who encourage the current practise.

(NOTE!! speaking for myself, not for other Red Hatters)

The solution I've settled upon is jgarzik@...hat.com for sign-offs, and 
my usual addresses (jeff@...zik, jgarzik@...ox) for all email 
communication and patch posting.

That makes it clear who is really signing off on the patches, while 
still ensuring that if I get fired or leave Red Hat, the flow of 
communication can be largely uninterrupted.

For those who don't know, to prevent sensitive information leaks, it is 
standard corporate policy for many companies these days to immediately 
yank an email address the minute an employee's status changes.

	Jeff


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