From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ben Dooks <ben-linux@fluff.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] SCSI fixes for 2.6.27-rc1
Date: Mon, 04 Aug 2008 17:11:23 -0400 [thread overview]
Message-ID: <4897707B.60404@garzik.org> (raw)
In-Reply-To: <20080804151533.6fb01b0a@lxorguk.ukuu.org.uk>
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@redhat.com for sign-offs, and
my usual addresses (jeff@garzik, jgarzik@pobox) 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
next prev parent reply other threads:[~2008-08-04 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 22:03 [GIT PATCH] SCSI fixes for 2.6.27-rc1 James Bottomley
2008-08-04 14:29 ` Ben Dooks
2008-08-04 14:15 ` Alan Cox
2008-08-04 21:11 ` Jeff Garzik [this message]
2008-08-04 14:44 ` James Bottomley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4897707B.60404@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ben-linux@fluff.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox