From: Jonathan Nieder <jrnieder@gmail.com>
To: Aaron Crane <git@aaroncrane.co.uk>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Sverre Rabbelier <srabbelier@gmail.com>,
Jacob Helwig <jacob.helwig@gmail.com>,
David Aguilar <davvid@gmail.com>,
Jay Soffian <jaysoffian@gmail.com>,
John Tapsell <johnflux@gmail.com>
Subject: Re: [PATCH] Documentation/SubmittingPatches: fix Gmail workaround advice
Date: Sun, 7 Feb 2010 15:54:28 -0600 [thread overview]
Message-ID: <20100207215311.GA2177@progeny.tock> (raw)
In-Reply-To: <bc341e101002071203x52bceaach8d42c6188630f1d1@mail.gmail.com>
Aaron Crane wrote:
> Junio C Hamano <gitster@pobox.com> wrote:
>> What I am trying to get at is to see if the current imap-send suggestion
>> is fundamentally unworkable with gmail. Perhaps they stopped supporting
>> imap. Perhaps the procedure never worked.
>
> As far as I can determine, the current imap-send suggestion is
> fundamentally unworkable with gmail at the moment. I don't know
> whether it ever used to work, though I've been assuming that it did.
I think it still works, or depending on your perspective, it never did.
As John Tapsell wrote in SubmittingPatches (commit 50dffd4e, 2009-02-19):
| GMail does not appear to have any way to turn off line wrapping in the web
| interface, so this will mangle any emails that you send. You can however
| use any IMAP email client to connect to the google imap server, and forward
| the emails through that. Just make sure to disable line wrapping in that
| email client. Alternatively, use "git send-email" instead.
I am not sure what that means about what SubmittingPatches should say:
should it explain both methods, then?
If I were doing it, I would put the information in the git-imap-send and
git-send-mail man pages as examples. That way, it would be visible for
people submitting patches to _other_ projects, too. The section in
Documentation/SubmittingPatches could be replaced with a pointer.
Jonathan
next prev parent reply other threads:[~2010-02-07 21:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-07 15:14 [PATCH] Documentation/SubmittingPatches: fix Gmail workaround advice Aaron Crane
2010-02-07 18:01 ` Jay Soffian
2010-02-07 18:37 ` Junio C Hamano
2010-02-07 20:03 ` Aaron Crane
2010-02-07 21:54 ` Jonathan Nieder [this message]
2010-02-07 22:16 ` Jonathan Nieder
2010-02-08 17:42 ` Junio C Hamano
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=20100207215311.GA2177@progeny.tock \
--to=jrnieder@gmail.com \
--cc=davvid@gmail.com \
--cc=git@aaroncrane.co.uk \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.helwig@gmail.com \
--cc=jaysoffian@gmail.com \
--cc=johnflux@gmail.com \
--cc=srabbelier@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).