-Please **do not** send pull-requests or open new issues on Github.
-
-Github is a downstream mirror and is not frequently monitored,
-all development is coordinated upstream on GNU resources.
-
-* Send general questions or suggestions to: coreutils@gnu.org .
-* Send bugs reports to: bug-coreutils@gnu.org .
-
-## Bug reports
+The preferred process for sending suggestions or bugs
+is to email coreutils@gnu.org or bug-coreutils@gnu.org respectively.
Before reporting a new bug, please check the following resources:
contains a list of some quirks and unexpected behavior (which are often
mistaken for bugs).
-* Online Manual:
- https://www.gnu.org/software/coreutils/manual/html_node/index.html
-
-* Search the archives for previous questions and answers:
-
- * Coreutils Mailing list (General usage and advice):
- https://lists.gnu.org/archive/html/coreutils/
-
- * Bug reports Mailing List:
- https://lists.gnu.org/archive/html/bug-coreutils/
-
-* Open Bugs:
- https://debbugs.gnu.org/cgi/pkgreport.cgi?which=pkg&data=coreutils
-
-* Translation related issues:
- https://translationproject.org/domain/coreutils.html
-
-
-## Effective bug reports
-
-* Include a descriptive subject line (e.g. the program with which
- you experience a problem, and what the problem is).
-* Include the version of the program (e.g. the output of `PROG --version`).
-* Include the operating system and the type of hardware you are using
- (e.g. the output of `uname -a`).
-* Include the exact command and parameters you have used.
-* Clearly explain what is the output you expected to get, and what is
- the actual result you encountered.
-* Include as much information as possible to reproduce the problem.
- If the problem happens on a very large input file, try to provide
- a minimal example (a subset of the input file) that still causes the problem.
- *Do not* include attachments over 40kB.
-* List policy is reply-to-all, and non-subscribers may post.
-* There may be a moderation delay for a first-time post, whether or not
- you subscribe.
-
-
-## Mailing List Etiquette
-
-When sending messages to coreutils@gnu.org or bug-coreutils@gnu.org :
-
-* Send messages as plain text.
-* Do not send messages encoded as HTML nor encoded as base64 MIME nor
- included as multiple formats.
-* Avoid sending large messages, such as log files, system call trace
- output, and other content resulting in messages over about 40 kB.
-* Avoid sending screenshots (e.g. PNG files). When reporting errors
- you encounter on the terminal, copy and paste the text to your message.
-
-
-
<!--
Copyright (C) 2017-2026 Free Software Foundation, Inc.
-Please *do not* send pull-requests or open new issues on Github.
-See "hacking resources" below for recommended alternatives.
+The preferred process for sending changes
+is to email coreutils@gnu.org or bug-coreutils@gnu.org respectively.
-Github is a downstream mirror and is not frequently monitored,
-all development is coordinated upstream on GNU resources.
+## Developer resources
-* Send general questions or suggestions to: coreutils@gnu.org .
-* Send bugs reports to: <bug-coreutils@gnu.org>
-
-Before sending the bug, please consult the FAQ and Mailing list
-archives (see below). Often these perceived bugs are simply due to
-wrong program usage.
-
-Please remember that development of Coreutils is a volunteer effort,
-and you can also contribute to its development. For information about
-contributing to the GNU Project, please read
-[How to help GNU](https://www.gnu.org/help/].
-
-
-## Getting Help
-
-* Coreutils FAQ: https://www.gnu.org/software/coreutils/faq/coreutils-faq.html
-
-* Coreutils Gotchas: https://www.pixelbeat.org/docs/coreutils-gotchas.html
- contains a list of some quirks and unexpected behavior (which are often
- mistaken for bugs).
-
-* Online Manual:
- https://www.gnu.org/software/coreutils/manual/html_node/index.html
-
-* Search the archives for previous questions and answers:
-
- * Coreutils Mailing list (General usage and advice):
- https://lists.gnu.org/archive/html/coreutils/
-
- * Bug reports Mailing List:
- https://lists.gnu.org/archive/html/bug-coreutils/
-
-* Open Bugs: https://debbugs.gnu.org/cgi/pkgreport.cgi?which=pkg&data=coreutils
-
-* Translation related issues:
- https://translationproject.org/domain/coreutils.html
-
-
-## Mailing List Etiquette
-
-When sending messages to coreutils@gnu.org or bug-coreutils@gnu.org :
-
-* Send messages as plain text.
-* Do not send messages encoded as HTML nor encoded as base64 MIME nor
- included as multiple formats.
-* Include a descriptive subject line.
-* Avoid sending large messages, such as log files, system call trace
- output, and other content resulting in messages over about 40 kB.
-* Avoid sending screenshots (e.g. PNG files). When reporting errors
- you encounter on the terminal, copy and paste the text to your message.
-* List policy is reply-to-all, and non-subscribers may post.
-* There may be a moderation delay for a first-time post, whether or not
- you subscribe.
-
-
-## Hacking resources
-
-files contain information about hacking and contributing to GNU coreutils:
+files containing information about contributing to GNU coreutils:
https://git.savannah.gnu.org/cgit/coreutils.git/tree/HACKING
https://git.savannah.gnu.org/cgit/coreutils.git/tree/README-hacking
Please read them first.
projects / thirdparty / coreutils.git / commitdiff
