From: "Rob Shearman" <robertshearman@gmail.com>
To: "Brian Gernhardt" <benji@silverinsanity.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 4/4] Documentation: Improve documentation for git-imap-send(1).
Date: Wed, 9 Jul 2008 13:05:34 +0100 [thread overview]
Message-ID: <1096648c0807090505l43e30f43pd348f95af4345956@mail.gmail.com> (raw)
In-Reply-To: <19AD9080-74BE-4147-8DF5-8A2937129B6D@silverinsanity.com>
2008/7/9 Brian Gernhardt <benji@silverinsanity.com>:
>
> On Jul 8, 2008, at 6:18 PM, Robert Shearman wrote:
>
>> +Using direct mode:
>>
>> +.........................
>> [imap]
>> - Host = imaps://imap.example.com
>> - User = bob
>> - Pass = pwd
>> - Port = 993
>> + folder = "[Gmail]/Drafts"
>> + host = imaps://imap.example.com
>> + user = bob
>> + pass = p4ssw0rd
>> + port = 123
>> sslverify = false
>> ..........................
>
> If you're going to use [Gmail]/Drafts as the example folder, shouldn't you
> just use mail.google.com as your example? Google themselves use
> username@gmail.com as an example[1], so that should be safe. So:
I'll fix it not to use "[Gmail]/Drafts" in the example as that is the
exception rather than the norm.
> And I also assume that someone has tried this with Gmail and it doesn't
> mangle the Drafts.
Yes, as specified in my previous email I tested with two different
IMAP servers, one of which was Gmail.
> I'd also move the sslverify option into the tunneling
> example, as it's more likely to be needed there.
Actually, the sslverify option is ignored in tunnel mode (since you're
likely to be using your own encryption with the tunnel). I'll document
this and other ignored options in a revised patch.
--
Rob Shearman
next prev parent reply other threads:[~2008-07-09 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 22:18 [PATCH 4/4] Documentation: Improve documentation for git-imap-send(1) Robert Shearman
2008-07-09 1:35 ` Brian Gernhardt
2008-07-09 12:05 ` Rob Shearman [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-09 21:29 Robert Shearman
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=1096648c0807090505l43e30f43pd348f95af4345956@mail.gmail.com \
--to=robertshearman@gmail.com \
--cc=benji@silverinsanity.com \
--cc=git@vger.kernel.org \
/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).