On Thu, Nov 16, 2017 at 5:23 AM, Greg Kroah-Hartman
wrote:
> Sometimes a single patch is the result of multiple authors. As git only
> can have one "author" of a patch, it is still good to properly give
> credit to the other developers of a commit. To address this, document
> the "Co-Developed-b
On Thu, 16 Nov 2017 14:23:09 +0100
Greg Kroah-Hartman wrote:
> Sometimes a single patch is the result of multiple authors. As git only
> can have one "author" of a patch, it is still good to properly give
> credit to the other developers of a commit. To address this, document
> the "Co-Develope
On Thu, Nov 16, 2017 at 02:23:09PM +0100, Greg Kroah-Hartman wrote:
> Sometimes a single patch is the result of multiple authors. As git only
> can have one "author" of a patch, it is still good to properly give
> credit to the other developers of a commit. To address this, document
> the "Co-Dev
On Thu, 16 Nov 2017, Greg Kroah-Hartman wrote:
> Sometimes a single patch is the result of multiple authors. As git only
> can have one "author" of a patch, it is still good to properly give
> credit to the other developers of a commit. To address this, document
> the "Co-Developed-by:" tag whic
Sometimes a single patch is the result of multiple authors. As git only
can have one "author" of a patch, it is still good to properly give
credit to the other developers of a commit. To address this, document
the "Co-Developed-by:" tag which can be used to show other authors of
the patch.
Note,