Bastien Guerry <[email protected]> writes: > On the other hand, I've tighten the rule so that a patch either has a > [PATCH] or a well-formatted patch (with git format-patch). > > So inline diffs and quick git diff > x.patch with no explicit [PATCH] > in the subject are not promoted as patch by BARK, they are just code > for comment in a thread. > > See https://tracker.orgmode.org/next/bark-manual.html
+1 > Yes, I've seen that too and I recommend not mixing subject labels. Note that we have some instances when subject labels do get mixed. Most likely because M-x org-submit-bug-report prepends [BUG] to the subject entered by the user. Sometimes, that subject already contains something like [FR]. Here is the latest example: https://list.orgmode.org/cao48bk-xx8qry826q7j_aabqaz18ilcpn+dpbpqgdb31nsm...@mail.gmail.com/T/#t I have also seen [BUG/FR] (when the author is not sure). -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
