X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=README.md;h=7534ccb5d659dbed803d16a50e3e4e522f0d4380;hb=6d3fea8f46568ae9f54bd50f9de2aeeb76e0cd23;hp=e5e3f29f00778beee9c70435975cc9824699f47f;hpb=d8f93ce802c31dde2b936d0626b636dc070e118b;p=platform%2Fupstream%2Fbtrfs-progs.git

diff --git a/README.md b/README.md
index e5e3f29..7534ccb 100644
--- a/README.md
+++ b/README.md
@@ -33,17 +33,18 @@ Reporting bugs
 --------------
 
 There are several ways, each has its own specifics and audience that can give
-feedback or work on a fix.
+feedback or work on a fix. The following list is sorted in the order of
+preference:
 
-* [bugzilla.kernel.org](https://bugzilla.kernel.org) -- (requires
-  registration), set the product to Filesystems and component Btrfs, please put
-  'btrfs-progs' into the subject so it's clear that it's not a kernel bug
-  report
+* [github issue tracker](https://github.com/kdave/btrfs-progs/issues)
 * to the mailing list *linux-btrfs@vger.kernel.org* -- (not required to
   subscribe), beware that the mail might get overlooked in other traffic
-* [github issue tracker](https://github.com/kdave/btrfs-sprogs/issues)
 * IRC (irc.freenode.net #btrfs) -- good for discussions eg. if a bug is already
   known, but reports could miss developers' attention
+* [bugzilla.kernel.org](https://bugzilla.kernel.org) -- (requires
+  registration), set the product to Filesystems and component Btrfs, please put
+  'btrfs-progs' into the subject so it's clear that it's not a kernel bug
+  report
 
 
 Development
@@ -70,10 +71,21 @@ the patches meet some criteria (often lacking in github contributions):
   effects of the bug or the fix, _how_ does an improvement help or the intended
   _usecase_
 * the **Signed-off-by** line: this documents who authored the change, you can read
-  more about the _The Developer's Certificate of Origin_ [here (chapter 11)](https://www.kernel.org/doc/Documentation/SubmittingPatches)
-
-**Exceptions**: documentation fixes or updates do not need much explanation so
-sticking to the above rules is not necessary. Github pull requests are OK.
+  more about the
+  [The Developer's Certificate of Origin (chapter 11)](https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin)
+  * if you are not used to the signed-off style, your contributions won't be
+    rejected just because of it's missing, the _Author:_ tag will be added as a
+    substitute in order to allow contributions without much bothering with
+    formalities
+
+Documentation updates
+---------------------
+
+Documentation fixes or updates do not need much explanation so sticking to the
+code rules in the previous section is not necessary. Github pull requests are
+OK, patches could be sent to me directly and not required to be also in the
+mailinglist. Pointing out typos via IRC also works, although might get
+accidentally lost in the noise.
 
 References
 ----------