1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586 |
- 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
- Before reporting a new bug, please check the following resources:
- * 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 behaviour (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-2018 Free Software Foundation, Inc.
- This program is free software: you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation, either version 3 of the License, or
- (at your option) any later version.
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
- You should have received a copy of the GNU General Public License
- along with this program. If not, see <https://www.gnu.org/licenses/>.
- -->
|