While some developers prefer to receive patches only on the mailing list, cc'ing is a common practice in other projects. Since it's easy enough to set up a mail filter for this, remove the paragraph for simplicity. Signed-off-by: Ján Tomko <jtomko(a)redhat.com&gt; --- docs/submitting-patches.rst | 5 ----- 1 file changed, 5 deletions(-) diff --git a/docs/submitting-patches.rst b/docs/submitting-patches.rst index 4cae82c771..be7f6253b6 100644 --- a/docs/submitting-patches.rst +++ b/docs/submitting-patches.rst @@ -56,11 +56,6 @@ well: $ git config sendemail.to libvir-list(a)redhat.com -As a rule, patches should be sent to the mailing list only: all -developers are subscribed to libvir-list and read it regularly, -so **please don't CC individual developers** unless they've -explicitly asked you to. - Avoid using mail clients for sending patches, as most of them will mangle the messages in some way, making them unusable for our purposes. Gmail and other Web-based mail clients are -- 2.39.0

Since we don't really say how to send patches using this diff algorithm, it only clutters the document about *submitting* patches. Signed-off-by: Ján Tomko <jtomko(a)redhat.com&gt; --- docs/submitting-patches.rst | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/submitting-patches.rst b/docs/submitting-patches.rst index be7f6253b6..7a8743b8d0 100644 --- a/docs/submitting-patches.rst +++ b/docs/submitting-patches.rst @@ -10,9 +10,7 @@ subject prefix. Alternatively, you may send patches using ``git send-email``. -Also, for code motion patches, you may find that -``git diff --patience`` provides an easier-to-read -patch. However, the usual workflow of libvirt developer is: +The usual workflow of libvirt developer is: :: -- 2.39.0