1Please **do not** send pull-requests or open new issues on Github.
2
3Github is a downstream mirror and is not frequently monitored,
4all development is coordinated upstream on GNU resources.
5
6* Send general questions or suggestions to: coreutils@gnu.org .
7* Send bugs reports to: bug-coreutils@gnu.org .
8
9## Bug reports
10
11Before reporting a new bug, please check the following resources:
12
13* Coreutils FAQ: https://www.gnu.org/software/coreutils/faq/coreutils-faq.html
14
15* Coreutils Gotchas: https://www.pixelbeat.org/docs/coreutils-gotchas.html
16  contains a list of some quirks and unexpected behavior (which are often
17  mistaken for bugs).
18
19* Online Manual:
20  https://www.gnu.org/software/coreutils/manual/html_node/index.html
21
22* Search the archives for previous questions and answers:
23
24   * Coreutils Mailing list (General usage and advice):
25     https://lists.gnu.org/archive/html/coreutils/
26
27   * Bug reports Mailing List:
28     https://lists.gnu.org/archive/html/bug-coreutils/
29
30* Open Bugs:
31  https://debbugs.gnu.org/cgi/pkgreport.cgi?which=pkg&data=coreutils
32
33* Translation related issues:
34  https://translationproject.org/domain/coreutils.html
35
36
37## Effective bug reports
38
39* Include a descriptive subject line (e.g. the program with which
40  you experience a problem, and what the problem is).
41* Include the version of the program (e.g. the output of `PROG --version`).
42* Include the operating system and the type of hardware you are using
43  (e.g. the output of `uname -a`).
44* Include the exact command and parameters you have used.
45* Clearly explain what is the output you expected to get, and what is
46  the actual result you encountered.
47* Include as much information as possible to reproduce the problem.
48  If the problem happens on a very large input file, try to provide
49  a minimal example (a subset of the input file) that still causes the problem.
50  *Do not* include attachments over 40kB.
51* List policy is reply-to-all, and non-subscribers may post.
52* There may be a moderation delay for a first-time post, whether or not
53  you subscribe.
54
55
56## Mailing List Etiquette
57
58When sending messages to coreutils@gnu.org or bug-coreutils@gnu.org :
59
60* Send messages as plain text.
61* Do not send messages encoded as HTML nor encoded as base64 MIME nor
62  included as multiple formats.
63* Avoid sending large messages, such as log files, system call trace
64  output, and other content resulting in messages over about 40 kB.
65* Avoid sending screenshots (e.g. PNG files). When reporting errors
66  you encounter on the terminal, copy and paste the text to your message.
67
68
69
70<!--
71Copyright (C) 2017-2023 Free Software Foundation, Inc.
72
73This program is free software: you can redistribute it and/or modify
74it under the terms of the GNU General Public License as published by
75the Free Software Foundation, either version 3 of the License, or
76(at your option) any later version.
77
78This program is distributed in the hope that it will be useful,
79but WITHOUT ANY WARRANTY; without even the implied warranty of
80MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
81GNU General Public License for more details.
82
83You should have received a copy of the GNU General Public License
84along with this program.  If not, see <https://www.gnu.org/licenses/>.
85-->
86