public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Manu Abraham <abraham.manu@gmail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: v4 [PATCH 00/10] Query DVB frontend delivery capabilities
Date: Mon, 12 Dec 2011 11:42:00 -0200	[thread overview]
Message-ID: <4EE604A8.8030507@redhat.com> (raw)
In-Reply-To: <CAHFNz9JC=r_hzkU1HOGvVkqHS-YZ0b7hatowgSaxpS7g58OVdA@mail.gmail.com>

On 12-12-2011 04:35, Manu Abraham wrote:
> On Sat, Dec 10, 2011 at 6:38 PM, Mauro Carvalho Chehab
> <mchehab@redhat.com>  wrote:
>> 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.verkuil@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:
>
>
> I don't have net access configured for the box where I do
> tests/on the testbox. The outgoing mail from my side is
> through the gmail web interface. If I don't attach the
> patches, gmail garbles those patches.

Not sure what you've meant by "net". Internet, or network, in general?

If you don't have an ethernet interface configured on your test box, you
can still put your git tree into a removable media (pen-driver or whatever)
and use it to transfer to your main machine, and then call git from it.

If you have Ethernet there, it is even simpler: from your main machine:

$ git pull remote:/patch/to/git my_branch

$ git send-email

Regards,
Mauro.

      reply	other threads:[~2011-12-12 13:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-10  4:41 v4 [PATCH 00/10] Query DVB frontend delivery capabilities Manu Abraham
2011-12-10 13:00 ` Mauro Carvalho Chehab
2011-12-10 13:08 ` Mauro Carvalho Chehab
2011-12-10 13:15   ` Antti Palosaari
2011-12-10 13:21     ` Mauro Carvalho Chehab
2011-12-10 16:21     ` Mauro Carvalho Chehab
2011-12-12  6:35   ` Manu Abraham
2011-12-12 13:42     ` Mauro Carvalho Chehab [this message]

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=4EE604A8.8030507@redhat.com \
    --to=mchehab@redhat.com \
    --cc=abraham.manu@gmail.com \
    --cc=linux-media@vger.kernel.org \
    /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