| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 5 Nov 2015 23:20:39 -0700 From: Eddie Kovsky <ewk@...ovsky.org> To: Jonathan Corbet <corbet@....net> Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, Darren Hart <dvhart@...radead.org> Subject: [PATCH 0/3] Documentation: Email client improvements A recent mailing list discussion about developer tools extended over to Google+. https://plus.google.com/+DarrenHart/posts/EbVFWJu3FK9 Several members of the kernel community felt that improving the email client documentation would make it easier for new developers to get started submitting patches. This series introduces three updates to help new contributors get Mutt working as quickly as possible. * Clarify that Gmail is acceptable for sending patches, as long as it is used without the web interface. * Add instructions for sending files directly from Mutt without use of a specific editor. * Add a minimal Mutt configuration to use Gmail's IMAP servers to send text email. I tested this configuration using a mockup local user and my own Gmail account. Thanks Eddie Eddie Kovsky (3): Clarify use of Gmail for emailing patches Add note on sending files directly with Mutt Add minimal Mutt config for using Gmail Documentation/email-clients.txt | 39 ++++++++++++++++++++++++++++++++++++++- 1 file changed, 38 insertions(+), 1 deletion(-) -- 2.6.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists