From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13731] New: Readline Patch is missing Author Information
Date: Wed, 07 Apr 2021 06:48:44 +0000 [thread overview]
Message-ID: <bug-13731-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13731
Bug ID: 13731
Summary: Readline Patch is missing Author Information
Product: buildroot
Version: 2021.02
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: contact at sesu8642.de
CC: buildroot at uclibc.org
Target Milestone: ---
Most patches contain headers which include information about the author (e.g.
"From: ..." or "Signed-off-by:"). We use this information to give credit to the
patch authors.
This patch is missing such information:
https://git.busybox.net/buildroot/tree/package/readline/0000-curses-link.patch
I suggest adding the information to the patch so that credit can be given
appopriately.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-04-07 6:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 6:48 bugzilla at busybox.net [this message]
2021-12-23 8:14 ` [Buildroot] [Bug 13731] Readline Patch is missing Author Information bugzilla
2022-03-15 8:51 ` bugzilla
2022-03-15 19:45 ` bugzilla
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=bug-13731-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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