From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: The authorship of each patch in a series
Date: Thu, 02 Sep 2021 09:13:55 +0200 [thread overview]
Message-ID: <2106510.qVkflTTfAS@localhost.localdomain> (raw)
Hi all,
Another developer and I collaborated to design and write a series of four
patches. Of course, we will both use the "Co-developed-by" and "Signed-off-
by" tags on each of the four works that make up the series.
However, there is a small problem that we would like to solve. Git-log only
displays a single name preceded by "Author:", so the reader of "git log --
pretty = short" will only be shown one of our names.
We would like git-log to show one name after "Author:" in 1/4 and 4/4 and the
other name in 2/4 and 3/4. This arbitrary breakdown is based on the fact that
approximately 80% -90% of the lines of code from the first patch group were
actually written by one of the two co-developers and approximately 80% -90%
of the second patch group was written by the other.
I guess Git will label anyone who submits the whole series as "Author"; works
like this or am I wrong? If so, I guess if my friend sends patches 0/4, 1/4
and 4/4 then I should find a way to send 2/4 and 3/4 somehow that makes it
clear to the maintainer, the tool that uses to apply the series, and the
reviewers, which also 2/4 and 3/4 belong to the same series as 0/4, 1/4 and
4/4.
How can we achieve this?
Thanks,
Fabio
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2021-09-02 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 7:13 Fabio M. De Francesco [this message]
2021-09-02 7:22 ` The authorship of each patch in a series Greg KH
2021-09-02 9:00 ` Fabio M. De Francesco
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=2106510.qVkflTTfAS@localhost.localdomain \
--to=fmdefrancesco@gmail.com \
--cc=kernelnewbies@kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.