All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: 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>,
	Jacob Helwig <jacob.helwig@gmail.com>
Subject: Re: [PATCH] Documentation/SubmittingPatches: Clarify Gmail section
Date: Thu, 8 Apr 2010 01:48:33 +0530	[thread overview]
Message-ID: <y2gf3271551004071318zb4ed7ef6o93a6c98c6009d8df@mail.gmail.com> (raw)
In-Reply-To: <7vwrwjav4h.fsf@alter.siamese.dyndns.org>

> 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.

No. An email client can sync with the drafts folder in GMail over
IMAP. However, sending the final email has to be done over SMTP.
The effect of "git imap-send" can be replicated by copy-pasting text
into the email client's compose interface. So, using "git imap-send"
seems like a bit of a roundabout way to me. There are some usecases
though (like queuing up patches as drafts before sending): so I'll add
a paragraph about this in my next revision.

-- Ram

  parent reply	other threads:[~2010-04-07 20:19 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
2010-04-07 20:18     ` Ramkumar Ramachandra [this message]
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=y2gf3271551004071318zb4ed7ef6o93a6c98c6009d8df@mail.gmail.com \
    --to=artagnon@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@aaroncrane.co.uk \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=gitzilla@gmail.com \
    --cc=jacob.helwig@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.