ISSUE_TEMPLATE.txt 3.2 KB

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