From: Jeff King <peff@peff.net>
To: John Tapsell <johnflux@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 2/6] Google has renamed the imap folder
Date: Thu, 19 Feb 2009 03:09:31 -0500 [thread overview]
Message-ID: <20090219080930.GA7774@coredump.intra.peff.net> (raw)
In-Reply-To: <200902190736.11912.johnflux@gmail.com>
On Thu, Feb 19, 2009 at 07:36:11AM +0000, John Tapsell wrote:
> [imap]
> - folder = "[Gmail]/Drafts"
> + folder = "[Google Mail]/Drafts"
I thought the consensus from the last patch was that it should stay
Gmail, as that is the name used in most countries?
> +You might need to instead use: folder = "[Google Mail]/Drafts" if you get an error
> +that the "Folder doesn't exist".
And this hunk certainly implies that's what you were shooting for.
-Peff
next prev parent reply other threads:[~2009-02-19 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 7:36 [PATCH 2/6] Google has renamed the imap folder John Tapsell
2009-02-19 8:09 ` Jeff King [this message]
2009-02-19 8:19 ` John Tapsell
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=20090219080930.GA7774@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=johnflux@gmail.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).