* README: List the corresponding email address on the first line of each sections. Note README is shown on the github project front page. * .github/ISSUE_TEMPLATE.txt: Adjust similarly. * .github/PULL_REQUEST_TEMPLATE.txt: Likewise. --- .github/ISSUE_TEMPLATE.txt | 5 +++-- .github/PULL_REQUEST_TEMPLATE.txt | 5 +++-- README | 18 ++++++++++-------- 3 files changed, 16 insertions(+), 12 deletions(-)
diff --git a/.github/ISSUE_TEMPLATE.txt b/.github/ISSUE_TEMPLATE.txt index 783c26769..e5cbf0228 100644 --- a/.github/ISSUE_TEMPLATE.txt +++ b/.github/ISSUE_TEMPLATE.txt @@ -1,5 +1,6 @@ -The preferred process for sending suggestions or bugs -is to email [email protected] or [email protected] respectively. +You can also email [email protected] for features/improvements +or [email protected] to discuss and track bugs. +Security sensitive issues should be sent to [email protected] Before reporting a new bug, please check the following resources: diff --git a/.github/PULL_REQUEST_TEMPLATE.txt b/.github/PULL_REQUEST_TEMPLATE.txt index 715fe5bd8..fbf1e41b7 100644 --- a/.github/PULL_REQUEST_TEMPLATE.txt +++ b/.github/PULL_REQUEST_TEMPLATE.txt @@ -1,5 +1,6 @@ -The preferred process for sending changes -is to email [email protected] or [email protected] respectively. +You can also send patches to [email protected] for features/improvements +or [email protected] for bug fixes. +Security sensitive patches should be sent to [email protected] ## Developer resources diff --git a/README b/README index f03aecdb9..22af246f2 100644 --- a/README +++ b/README @@ -59,9 +59,10 @@ is in texinfo form in the doc directory. *************** -Feature requests: +General requests: --------------- +Send feature requests, questions, and comments etc. to [email protected]. If you would like to add a new feature, please try to get some sort of consensus that it is a worthwhile change. One way to do that is to send mail to [email protected] including as much description and justification @@ -71,23 +72,24 @@ previously discussed but ultimately rejected feature requests at: https://www.gnu.org/software/coreutils/rejected_requests.html +*************** +Security issues: +--------------- + +Send security sensitive reports to [email protected]. +That is monitored by all maintainers and should be responded to promptly. + *************** Reporting bugs: --------------- -Send bug reports, questions, comments, etc. to [email protected]. +Send bug reports to [email protected]. To suggest a patch, see the files README-hacking and HACKING for tips. All of these programs except 'test' recognize the '--version' option. When reporting bugs, please include in the subject line both the package name/version and the name of the program for which you found a problem. -If you have a problem with 'sort', try running 'sort --debug', as it -can often help find and fix problems without having to wait for an -answer to a bug report. If the debug output does not suffice to fix -the problem on your own, please compress and attach it to the rest of -your bug report. - IMPORTANT: if you take the time to report a test failure, please be sure to include the output of running 'make check' in verbose mode for each failing test. For example, -- 2.55.0
