docker – Blame information for rev 62

Subversion Repositories:
Rev:
Rev Author Line No. Line
62 office 1 # Support [![](https://isitmaintained.com/badge/resolution/crazy-max/docker-rtorrent-rutorrent.svg)](https://isitmaintained.com/project/crazy-max/docker-rtorrent-rutorrent)
2  
3 ## Reporting an issue
4  
5 Please do a search in [open issues](https://github.com/crazy-max/docker-rtorrent-rutorrent/issues?utf8=%E2%9C%93&q=) to see if the issue or feature request has already been filed.
6  
7 If you find your issue already exists, make relevant comments and add your [reaction](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments). Use a reaction in place of a "+1" comment.
8  
9 :+1: - upvote
10  
11 :-1: - downvote
12  
13 If you cannot find an existing issue that describes your bug or feature, submit an issue using the guidelines below.
14  
15 ## Writing good bug reports and feature requests
16  
17 File a single issue per problem and feature request.
18  
19 * Do not enumerate multiple bugs or feature requests in the same issue.
20 * Do not add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar, but have different causes.
21  
22 The more information you can provide, the more likely someone will be successful reproducing the issue and finding a fix.
23  
24 You are now ready to [create a new issue](https://github.com/crazy-max/docker-rtorrent-rutorrent/issues/new/choose)!
25  
26 ## Closure policy
27  
28 * Support directly related to rTorrent or ruTorrent will not be provided if your problem is not related to the operation of this image.
29 * Issues that don't have the information requested above (when applicable) will be closed immediately and the poster directed to the support guidelines.
30 * Issues that go a week without a response from original poster are subject to closure at my discretion.