On 10-12-2011 11:15, Antti Palosaari wrote:
On 12/10/2011 03:08 PM, Mauro Carvalho Chehab wrote:
A separate issue: please, don't send patches like that as attachment. It
makes
hard for people review. Instead, you should use git send-email. There's
even
an example there (at least on git version 1.7.8) showing how to set it for
Google:
$ git help send-email
...
EXAMPLE
Use gmail as the smtp server
To use git send-email to send your patches through the GMail SMTP
server, edit ~/.gitconfig to specify your
account settings:
[sendemail]
smtpencryption = tls
smtpserver = smtp.gmail.com
smtpuser = yourn...@gmail.com
smtpserverport = 587
Once your commits are ready to be sent to the mailing list, run the
following commands:
$ git format-patch --cover-letter -M origin/master -o outgoing/
$ edit outgoing/0000-*
$ git send-email outgoing/*
I have SMTP which requires login over SSL. I am not sure if Git send-email
event supports that
It does.
but even if it supports I don't like idea to put my clear text password to some
config file.
You could then write a small script:
#!/bin/bash
echo -n Password:
read
git send-email --smtp-pass $REPLY
This would avoid storing your password at the bash history or at a config file.
That's why I have used Thunderbird with External Editor and it sucks :/
git send-email will likely work a way better than that.
Regards,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
