On 10-12-2011 02:41, Manu Abraham wrote:
Hi,
As discussed prior, the following changes help to advertise a
frontend's delivery system capabilities.
Sending out the patches as they are being worked out.
The following patch series are applied against media_tree.git
after the following commit
commit e9eb0dadba932940f721f9d27544a7818b2fa1c5
Author: Hans Verkuil<hans.verk...@cisco.com>
Date: Tue Nov 8 11:02:34 2011 -0300
[media] V4L menu: add submenu for platform devices
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/*
Note: the following perl modules are required Net::SMTP::SSL,
MIME::Base64 and Authen::SASL
...
In practice, I generally just do this here:
$ git send-email [some obj reference]
For example, when I want to send the last 3 patches, I just do:
$ git send-email HEAD^1^1^1
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
