From: Pierre Habouzit <madcoder@debian.org>
To: Tom Preston-Werner <tom@github.com>
Cc: "Santi Béjar" <santi@agolina.net>,
git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH] add instructions on how to send patches to the mailing list with Gmail
Date: Sun, 02 Nov 2008 10:10:06 +0100 [thread overview]
Message-ID: <20081102091006.GA4066@artemis> (raw)
In-Reply-To: <b97024a40811011340s92a1c24jb81b75dfb25e43c5@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2030 bytes --]
On Sat, Nov 01, 2008 at 08:40:27PM +0000, Tom Preston-Werner wrote:
> On Sat, Nov 1, 2008 at 3:00 AM, Santi Béjar <santi@agolina.net> wrote:
> > On Sat, Nov 1, 2008 at 8:28 AM, Tom Preston-Werner <tom@github.com> wrote:
> >> Gmail is one of the most popular email providers in the world. Now that Gmail
> >> supports IMAP, sending properly formatted patches via `git imap-send` is
> >> trivial. This section in SubmittingPatches explains how to do so.
> >>
> >> Signed-off-by: Tom Preston-Werner <tom@github.com>
> >> ---
> >> Documentation/SubmittingPatches | 27 +++++++++++++++++++++++++++
> >> 1 files changed, 27 insertions(+), 0 deletions(-)
> >>
> >> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> >> index a1e9100..f0295c6 100644
> >> --- a/Documentation/SubmittingPatches
> >> +++ b/Documentation/SubmittingPatches
> >> @@ -456,3 +456,30 @@ This should help you to submit patches inline using KMail.
> >>
> >> 5) Back in the compose window: add whatever other text you wish to the
> >> message, complete the addressing and subject fields, and press send.
> >> +
> >> +
> >> +Gmail
> >> +-----
> >> +
> >> +Submitting properly formatted patches via Gmail is simple now that
> >> +IMAP support is available. First, edit your ~/.gitconfig to specify your
> >> +account settings:
> >> +
> >> +[imap]
> >> + folder = "[Gmail]/Drafts"
> >> + host = imaps://imap.gmail.com
> >> + user = user@gmail.com
> >> + pass = p4ssw0rd
> >> + port = 993
> >> + sslverify = false
> >
> > Warning: It is not secure.
>
> It is true that the certificate is not verified, but since the patches
> are destined for a public mailing list, this does not represent a
> large problem.
What he means is that the password is cleartext ;)
(I think)
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-11-02 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 7:28 [PATCH] add instructions on how to send patches to the mailing list with Gmail Tom Preston-Werner
2008-11-01 10:00 ` Santi Béjar
2008-11-01 20:40 ` Tom Preston-Werner
2008-11-02 9:10 ` Pierre Habouzit [this message]
2008-11-02 15:01 ` Fredrik Skolmli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081102091006.GA4066@artemis \
--to=madcoder@debian.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=santi@agolina.net \
--cc=tom@github.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).