How do gmail users try out patches from this list?

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.

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.

Use the POP or IMAP to access your gmail account.

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

Heya,

On Tue, Aug 11, 2009 at 13:47, Emmanuel Trillaud[off-list ref] wrote:

To quote Documentation/SubmittingPatches:

Not relevant, these instructions are for the other way around; that
is, sending your patches _to_ the ML, rather than getting patches
_from_ the ML.

-- 
Cheers,

Sverre Rabbelier

Huuu! Sorry!
I read your mail too fast.
If you manage to save the interresting mails localy in the mailbox
format (claws mail and thunderbird can do that), you can
then use 'git am' to apply the patches (an example:
http://www.kernel.org/pub/software/scm/git/docs/everyday.html#Integrator).

Best regards

Emmanuel Trillaud

Le Tue, 11 Aug 2009 13:55:38 -0700,
Sverre Rabbelier [off-list ref] a écrit :

Heya,

On Tue, Aug 11, 2009 at 13:47, Emmanuel Trillaud[off-list ref]
wrote:

quoted

To quote Documentation/SubmittingPatches:

Not relevant, these instructions are for the other way around; that
is, sending your patches _to_ the ML, rather than getting patches
_from_ the ML.

The 11/08/09, skillzero@gmail.com wrote:

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?

It doesn't rely on your address mail provider but on your local email
workflow/MUA.

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?

Yes, that's what most users do. As I use local maildirs instead of
mailboxes, I copy the patches (from mutt) into a dedicated maildir (one
per project) and directly 'git am' the e-mails.


-- 
Nicolas Sebrecht

On Tuesday 11 August 2009 16:14:08 Nicolas Sebrecht wrote:

The 11/08/09, skillzero@gmail.com wrote:

quoted

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?

It doesn't rely on your address mail provider but on your local email
workflow/MUA.

I'm not in this situation, but my guess is that a lot of people use gmail 
primarily through the web interface (e.g. because of corporate firewalls or 
some other reason). Maybe someone in that situation should make an new "git 
imap-am" command? Kind of the reverse to imap-send. Just a thought. =)

Wesley J. Landaker venit, vidit, dixit 12.08.2009 03:17:

On Tuesday 11 August 2009 16:14:08 Nicolas Sebrecht wrote:

quoted

The 11/08/09, skillzero@gmail.com wrote:

quoted

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?

It doesn't rely on your address mail provider but on your local email
workflow/MUA.

I'm not in this situation, but my guess is that a lot of people use gmail 
primarily through the web interface (e.g. because of corporate firewalls or 
some other reason). Maybe someone in that situation should make an new "git 
imap-am" command? Kind of the reverse to imap-send. Just a thought. =)

Well, if they can't do imap (because of a firewall) git can't do imap...

I guess for them (webmail users) it would be better if we attached
patches, but we don't do that here. In any case, our list is mirrored on
gmane, and you can use the interface there. For example, you get the
first message in this thread using the gmane id or the message id like this:

http://article.gmane.org/gmane.comp.version-control.git/125591
http://mid.gmane.org/2729632a0908111343v73fa475fqb6353dcf2f718101@mail.gmail.com

If you add /raw to those URLs you get the original message so that you
can happily wget/curl/browse and save away.

Michael

2009/8/11  [off-list ref]:

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.

Yep, show original, copy and paste and git apply. Personally I would
prefer to fetch changes using, oh, I don't know, some kind of dvcs
tool... 8-) It means I don't tend to build and test many patch series
until they get merged.

It's a pity there's a patchwork server for many kernel.org projects,
but not for the git mailing list 8-(

http://patchwork.kernel.org/

http://patchwork.kernel.org/help/pwclient/

http://gitster.livejournal.com/18696.html

On Tue, Aug 11, 2009 at 22:43, [off-list ref] wrote:

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.

"Show original", save the page into a file (it's text/plain), remove
the first line
of spaces, and do "git am" on the file. Works every time.

On 8/12/09, Michael J Gruber [off-list ref] wrote:

 I guess for them (webmail users) it would be better if we attached
 patches, but we don't do that here. In any case, our list is mirrored on
 gmane, and you can use the interface there. For example, you get the
 first message in this thread using the gmane id or the message id like this:

 http://article.gmane.org/gmane.comp.version-control.git/125591
 http://mid.gmane.org/2729632a0908111343v73fa475fqb6353dcf2f718101@mail.gmail.com

 If you add /raw to those URLs you get the original message so that you
 can happily wget/curl/browse and save away.

even better http://download.gmane.org/gmane.comp.version-control.git/N/M
[1] (where N and M is the gmane message ID range) gives you mbox
format of a series of consecutive messages.

[1] http://gmane.org/export.php
-- 
Duy