Getting things like SPF and DKIM right for this would be nigh-on
impossible, plus it would mean sysadmins would have to let patchwork
send email, which is a risk to the reputation of their systems.

Let's just aim for being a read-only representation of the mailing
list for now.

Signed-off-by: Daniel Axtens <d...@axtens.net>
---
 docs/usage/design.rst | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/docs/usage/design.rst b/docs/usage/design.rst
index 2d8fea7d9a43..56719eed4576 100644
--- a/docs/usage/design.rst
+++ b/docs/usage/design.rst
@@ -10,10 +10,6 @@ be two forums of discussion on patches, which fragments the 
patch review
 process. Developers who don't use Patchwork would get left out of the
 discussion.
 
-However, a future development item for Patchwork is to facilitate on-list
-commenting, by providing a "send a reply to the list" feature for logged-in
-users.
-
 Don't pollute the project's changelogs with Patchwork poop
 ----------------------------------------------------------
 
-- 
2.14.1

_______________________________________________
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork

Reply via email to