linux-kernel - [RFC] Add a "Co-authored-by" commit tag

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>] [day] [month] [year] [list]

Date:	Wed, 23 Jan 2013 15:48:02 +0100 (CET)
From:	Guennadi Liakhovetski <g.liakhovetski@....de>
To:	linux-kernel@...r.kernel.org
cc:	Greg KH <greg@...ah.com>, Randy Dunlap <rdunlap@...otime.net>,
	Jonathan Corbet <corbet@....net>,
	Sylwester Nawrocki <sylvester.nawrocki@...il.com>
Subject: [RFC] Add a "Co-authored-by" commit tag

Hi all

In most cases we work on our patches from the beginning to the end, but 
from time to time it happens, that someone originates a patch but then 
becomes (temporarily) unable to continue with new reviews, so, someone 
picks it up from there and brings to a final form. Or simply even several 
persons work closely on one patch. A yet another case is, when someone 
posts a rough first version of a patch, but then someone else heavily 
reworks it and becomes the actual submitting author of the patch, still, 
the original author should be mentioned somehow too.

Currently we can do something like

From: Original Author <...>

Signed-off-by: Original Author <...>
[contributor-2@...: continued patch development since v2]
Signed-off-by: New Contributor <contributor-2@...>

But is this sufficient, wouldn't a "Co-authored-by" tag be a better match 
for similar situations?

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
--
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/