From: "Thomas Schmitt" <scdbackup@gmx.net>
To: kernelnewbies@kernelnewbies.org
Cc: ebashinskii@mail.ru
Subject: Re: Kernel bug tracker
Date: Mon, 06 Sep 2021 11:04:48 +0200 [thread overview]
Message-ID: <15518361820812602362@scdbackup.webframe.org> (raw)
In-Reply-To: <1630915906.387388454@f701.i.mail.ru>
Hi,
> 1. When submitting the patch should I include you in the copy
> as the original author?
I guess this is more a question for the experienced patch submitters.
My cheat sheet points to
https://www.kernel.org/doc/html/v5.10/process/submitting-patches.html
The code change is trivial enough that i do not claim authorship.
So how about
Suggested-by: Thomas Schmitt <scdbackup@gmx.net>
I found the bug and suggested an obvious fix.
The most kernel merit i can claim is that i grepped through the kernel
sources for callers of iso_date() and found them all ready for the change
of result type.
So maybe
Co-developed-by: Thomas Schmitt <scdbackup@gmx.net>
Signed-off-by: Thomas Schmitt <scdbackup@gmx.net>
But on the other hand you should verify my claims in 0000-cover-letter.patch
before posting your patch. A year has passed since i did my research and
testing.
So my statements create not more authorship than a detailed bug report would
do.
Have a nice day :)
Thomas
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-09-06 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1630659351.685242253@f502.i.mail.ru>
2021-09-03 11:00 ` Kernel bug tracker Thomas Schmitt
2021-09-03 15:55 ` Valdis Klētnieks
2021-09-03 16:58 ` Thomas Schmitt
2021-09-05 10:10 ` Re[2]: " Adverg Ebashinskii
2021-09-05 11:48 ` Thomas Schmitt
2021-09-05 12:08 ` Thomas Schmitt
2021-09-06 8:11 ` Re[2]: " Adverg Ebashinskii
2021-09-06 9:04 ` Thomas Schmitt [this message]
2021-09-05 11:57 ` Thomas Schmitt
[not found] <1630220663.155756289@f748.i.mail.ru>
2021-08-29 8:50 ` Anatoly Pugachev
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=15518361820812602362@scdbackup.webframe.org \
--to=scdbackup@gmx.net \
--cc=ebashinskii@mail.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).