git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Documentation/SubmittingPatches: Clarify Gmail section

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 7, 2010, 20:02 UTC
Message-ID
<7vwrwjav4h.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1270668793-2187-2-git-send-email-artagnon@gmail.com>
Ramkumar Ramachandra <artagnon@gmail.com> writes:
> The web interface mangles patches no matter what. Replace paragraph
> about "git imap-send" with another one about "git send-email".

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.

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.

Show 21 quoted lines
> +GMail does not have any way to turn off line wrapping in the web
> +interface, so this will mangle any emails that you send.  You can
> +either configure an email client that that doesn't break lines to use
> +the GMail SMTP server, or use "git send-email" to achieve the same
> +effect.
> +
> +To use "git send-email", edit ~/.gitconfig to specify your account
> +settings:
> +
> +[sendemail]
> +	smtpencryption = tls
> +	smtpserver = smtp.gmail.com
> +	smtpuser = user@gmail.com
> +	smtppass = p4ssw0rd
> +	smtpserverport = 587
> +
> +Once your commits are ready to send to the mailing list, run the
> +following commands:
> +
> +	$ git format-patch --no-color -C -M origin/master -o outgoing/
> +	$ git send-email --compose outgoing/*
Previous: Ramkumar RamachandraNext: Jacob Helwig
Message 3 of 7 in “Documentation/SubmittingPatches: Clarify Gmail section”
  1. Documentation/SubmittingPatches: Clarify Gmail sectionRamkumar Ramachandra, Apr 7, 2010
  2. Documentation/SubmittingPatches: Clarify Gmail sectionRamkumar Ramachandra, Apr 7, 2010
  3. Junio C HamanoApr 7, 2010
  4. Jacob HelwigApr 7, 2010
  5. Ramkumar RamachandraApr 7, 2010
  6. Jon SeymourApr 7, 2010
  7. Junio C HamanoApr 7, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.