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:	Tue, 03 Mar 2015 22:52:17 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Ciprian Ciubotariu <cheepeero@....net>
Cc:	linux-kernel@...r.kernel.org, Jiri Kosina <jkosina@...e.cz>,
	linux-input@...r.kernel.org,
	Bruno Premont <bonbons@...ux-vserver.org>
Subject: Re: [PATCH] Add drivers for Logitech G110, G13, G15v2 and G19

On Mon, 2015-02-23 at 22:47 +0200, Ciprian Ciubotariu wrote:
> On Saturday 21 February 2015 18:21:20 Paul Bolle wrote:
> > Apparently Alistair Buxton, Rick L Vinyard Jr, and Thomas Berger were
> > involved with this code too. There's no mention of them in the commit
> > explanation. They're also not CC-ed.
> 
> The driver moved around with a lot of people contributing small changes. Some 
> (including myself) chose to add a MODULE_AUTHOR line, but others didn't. While 
> I can list all contributors from the git fork I found, I am sure I won't be 
> able to track those before the git fork.
> 
> What is the appropriate follow-up? Add all contributors to MODULE_AUTHOR? 
> Leave them as is? Which ones should be CC'ed?

It depends, I think, on what Jiri is comfortable with for the HID tree.
And I can't read Jiri's mind.

Personally I would add a line or two to the commit explanation detailing
how this patch ended up in your tree. And CC-ing the people previously
working on this patch will cost you next to nothing, so I'd do that too.


Paul Bolle

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