Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1263762 > unrolled thread

[PATCH 0/3] Documentation: Email client improvements

Started byEddie Kovsky <ewk@edkovsky.org>
First post2015-11-06 07:30 +0100
Last post2015-11-06 08:20 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH 0/3] Documentation: Email client improvements Eddie Kovsky <ewk@edkovsky.org> - 2015-11-06 07:30 +0100
    Re: [PATCH 0/3] Documentation: Email client improvements Darren Hart <dvhart@infradead.org> - 2015-11-06 08:20 +0100

#1263762 — [PATCH 0/3] Documentation: Email client improvements

FromEddie Kovsky <ewk@edkovsky.org>
Date2015-11-06 07:30 +0100
Subject[PATCH 0/3] Documentation: Email client improvements
Message-ID<qrIH8-S8-7@gated-at.bofh.it>
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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1263800

FromDarren Hart <dvhart@infradead.org>
Date2015-11-06 08:20 +0100
Message-ID<qrJtw-1pc-19@gated-at.bofh.it>
In reply to#1263762
On Thu, Nov 05, 2015 at 11:20:39PM -0700, Eddie Kovsky wrote:
> 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

Thank you Eddie!

Each of these patches is an incremental improvement and adds useful information
to the documentation.

For the series:

Reviewed-by: Darren Hart <dvhart@infradead.org>

> 
> 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
> 
> 

-- 
Darren Hart
Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web