git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jeff King <peff@peff.net>
Cc: Knittl <knittl89@googlemail.com>, git@vger.kernel.org
Subject: Re: [PATCH] Show branch information in short output of git status
Date: Tue, 25 May 2010 10:10:54 +0200	[thread overview]
Message-ID: <4BFB860E.1070006@drmicha.warpmail.net> (raw)
In-Reply-To: <20100525072240.GA20408@coredump.intra.peff.net>

Jeff King venit, vidit, dixit 25.05.2010 09:22:
> On Tue, May 25, 2010 at 09:19:18AM +0200, Michael J Gruber wrote:
> 
>> I'm really wondering what the problem is with git-send-email + GMail's
>> smtp. I'm not saying there is none: I'm just observing that we seem to
>> attract a lot of new contributors lately and that the email-inline-patch
>> requirement seems to be a hurdle to quite a few. I've created a mob
>> branch at
> 
> I don't use gmail, but my impression was that the problem is one of:
> 
>   1. pushing to gmail's drafts folder via imap, and then using the web
>      interface to send the email
> 
>   2. cutting and pasting into the web interface
> 
> I would hope that sending directly via SMTP with git-send-email would
> not get munged. That is pretty broken otherwise.

Well, I know what the problem is with GMail's IMAP and web, but it's
good to have it summed up this concisely ;)

I'm wondering what the problem is with GMail's SMTP: Technically there
is none, but people shy away from using it (together with
git-send-email). It does not even require setting up an MTA like
sendmail or msmtp. But, apparently, this is a hurdle, which is why I
brought up the mob-auto-send.

Michael

  reply	other threads:[~2010-05-25  8:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-02  9:13 [PATCH] Show branch information in short output of git status Knittl
2010-05-05  5:06 ` Jeff King
2010-05-06 12:24   ` Knittl
2010-05-07 16:05     ` Knittl
2010-05-12 13:35     ` Jeff King
2010-05-14  6:54       ` Knittl
2010-05-23  9:23         ` Jeff King
2010-05-25  7:19           ` Michael J Gruber
2010-05-25  7:22             ` Jeff King
2010-05-25  8:10               ` Michael J Gruber [this message]
2010-05-25  8:30               ` [PATCH] Documentation/SubmittingPatches: clarify GMail section and SMTP Michael J Gruber
2010-05-25  9:25                 ` Jeff King
2010-05-25  9:47                   ` Ævar Arnfjörð Bjarmason
  -- strict thread matches above, loose matches on Subject: below --
2010-05-02 10:10 [PATCH] Show branch information in short output of git status Knittl
     [not found] <AANLkTinNYcuiyRpgMGpQAEaStj2MDg9UooozooLPwv_0@mail.gmail.com>
2010-05-25 13:45 ` Michael J Gruber
2010-05-25 14:03   ` Michael J Gruber

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=4BFB860E.1070006@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=knittl89@googlemail.com \
    --cc=peff@peff.net \
    /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).