From: Emmanuel Trillaud <etrillaud@gmail.com>
To: skillzero@gmail.com
Cc: git@vger.kernel.org
Subject: Re: How do gmail users try out patches from this list?
Date: Tue, 11 Aug 2009 22:47:17 +0200 [thread overview]
Message-ID: <20090811224717.785dcd27@eleanor> (raw)
In-Reply-To: <2729632a0908111343v73fa475fqb6353dcf2f718101@mail.gmail.com>
To quote Documentation/SubmittingPatches:
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.
Submitting properly formatted patches via Gmail is simple now that
IMAP support is available. First, edit your ~/.gitconfig to specify your
account settings:
[imap]
folder = "[Gmail]/Drafts"
host = imaps://imap.gmail.com
user = user@gmail.com
pass = p4ssw0rd
port = 993
sslverify = false
You might need to instead use: folder = "[Google Mail]/Drafts" if you get
an error that the "Folder doesn't exist".
Next, ensure that your Gmail settings are correct. In "Settings" the
"Use Unicode (UTF-8) encoding for outgoing messages" should be checked.
Once your commits are ready to send to the mailing list, run the following
command to send the patch emails to your Gmail Drafts folder.
$ git format-patch -M --stdout origin/master | git imap-send
Go to your Gmail account, open the Drafts folder, find the patch email,
fill in the To: and CC: fields and send away!
Best Regards
Emmanuel Trillaud
Le Tue, 11 Aug 2009 13:43:13 -0700,
skillzero@gmail.com a écrit :
> Sorry if this is dumb question, but I didn't see any good info in my
> searches.
>
> How do gmail users normally apply patches that come through the list?
> Do you just manually copy and paste the email to patch files and use
> git apply? Do you use a tool to export to mbox files and use git am?
>
> I've been just doing it manually via copy and paste, but it's kinda
> tedious. --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-08-11 20:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 20:43 How do gmail users try out patches from this list? skillzero
2009-08-11 20:47 ` Emmanuel Trillaud [this message]
2009-08-11 20:55 ` Sverre Rabbelier
2009-08-11 21:24 ` Emmanuel Trillaud
2009-08-11 20:47 ` Russ Dill
2009-08-11 22:14 ` Nicolas Sebrecht
2009-08-12 1:17 ` Wesley J. Landaker
2009-08-12 8:23 ` Michael J Gruber
2009-08-12 8:43 ` Mike Ralphson
2009-08-12 13:43 ` Nguyen Thai Ngoc Duy
2009-08-12 12:51 ` Alex Riesen
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=20090811224717.785dcd27@eleanor \
--to=etrillaud@gmail.com \
--cc=git@vger.kernel.org \
--cc=skillzero@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).