Documentation: Email client improvements
Status from this message: I've applied the other two, though, thanks.
Get series with b4
b4 am 20151106062039.GA16257@athenaVersions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | Documentation: Clarify use of Gmail for emailing patchesDocumentation/ | +2 | 1 reply | |
| 2/3 | Documentation: Add note on sending files directly with MuttDocumentation/ | +4 | 0 replies | |
| 3/3 | Documentation: Add minimal Mutt config for using GmailDocumentation/ | +32 | 0 replies |
Reviews trailers per patch
None of the 3 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Darren Hart |
|---|---|
| Series | R-b |
| 1/3 | |
| 2/3 | |
| 3/3 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [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