rsync bug-tracking
Please use this checklist combined with the help on the
issues and debugging page before
reporting a bug. Thanks!
- If you're not using the latest released version, please upgrade before
reporting a bug.
- If you're using the latest released version, consult the
NEWS file from the git repository to see if what
you're seeing has already been handled in the version under development.
- It is also helpful to search the bug reports at both the new
GitHub issues tracker and the old
bugzilla database
to see if the problem is already known.
- See also the issues and debugging page to
help you figure out if what you're seeing is a known bug and perhaps to
help diagnose what is going wrong.
- Discuss the bug on the
rsync mailing list
(which is at rsync@lists.samba.org) to help you figure out if what
you're seeing is really a bug or a mistake.
- There are several patches for features that are under consideration that
can be found in the rsync-patches repo.
- If you haven't already done so, please take a couple of minutes to read Simon Tatham's
advice on how to report bugs.
To report a bug or make suggestions, use one of these methods:
- The mailing list (mentioned above) is a good resource for discussing
bugs and suggesting new features. It accepts patches (typically as MIME
attachments), but for fixes is often easier to attach a patch to an
appropriate GitHub issue report or use a pull request. Note that there is
no mandate to use pull requests for patches, as that can be a pretty high
bar of git know-how that not everyone needs to be familiar with.
- If you'd like to see a bug-report or feature-request get officially noted,
create an issue on GitHub
(this does require that you have created a GitHub account). If you want to
stay abreast of what's going on with the issues, make use of the GitHub
subscriptions to pick and choose what kind of notifications you want to
receive (e.g. just a single issue, all issues, all rsync activity, etc.).
Thanks for helping out!
|
