From: Jacob Helwig <jacob.helwig@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
John Tapsell <johnflux@gmail.com>,
Aaron Crane <git@aaroncrane.co.uk>,
A Large Angry SCM <gitzilla@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH] Documentation/SubmittingPatches: Clarify Gmail section
Date: Wed, 7 Apr 2010 13:06:42 -0700 [thread overview]
Message-ID: <x2m8c9a061004071306n807b8010i12983bb2d6a144f9@mail.gmail.com> (raw)
In-Reply-To: <7vwrwjav4h.fsf@alter.siamese.dyndns.org>
On Wed, Apr 7, 2010 at 13:02, Junio C Hamano <gitster@pobox.com> wrote:
> My impression has been that people are using MUAs that do not corrupt
> patches and are capable of using IMAP drafts folders with Gmail, without
> ever touching their patch-breaking web interface, and the description you
> removed was meant for them.
>
> Is the web interface the _only_ way to interact with IMAP drafts on Gmail?
> If that is the case, your patch (or Aaron's earlier attempt) to make the
> document not to talk about imap-send in the context of Gmail makes sense.
>
The web interface isn't the only way. I use the IMAP drafs all the
time with mutt, and most mutt + gmail instructions I've seen online
setup this behavior.
> Even if it were not the case, as long as only very few people use IMAP
> drafts on Gmail via MUAs not their web interface, I am fine with your
> change to add send-email recipe to help Gmail users.
>
next prev parent reply other threads:[~2010-04-07 20:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 19:33 [PATCH v2] Documentation/SubmittingPatches: Clarify Gmail section Ramkumar Ramachandra
2010-04-07 19:33 ` [PATCH] " Ramkumar Ramachandra
2010-04-07 20:02 ` Junio C Hamano
2010-04-07 20:06 ` Jacob Helwig [this message]
2010-04-07 20:18 ` Ramkumar Ramachandra
2010-04-07 22:23 ` Jon Seymour
2010-04-07 22:59 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2010-04-07 17:52 Ramkumar Ramachandra
2010-04-07 18:08 ` Ramkumar Ramachandra
2010-04-07 19:09 ` Junio C Hamano
2010-04-07 20:00 ` Ramkumar Ramachandra
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=x2m8c9a061004071306n807b8010i12983bb2d6a144f9@mail.gmail.com \
--to=jacob.helwig@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=artagnon@gmail.com \
--cc=git@aaroncrane.co.uk \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=gitzilla@gmail.com \
--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).