From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Ezequiel Garcia <elezegarcia@gmail.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [GIT PULL FOR 3.9] em28xx videobuf2 support and v4l2-compliance fixes
Date: Sat, 05 Jan 2013 13:49:41 +0100 [thread overview]
Message-ID: <50E82165.1000100@googlemail.com> (raw)
In-Reply-To: <CAGoCfiyEUQs3J7x2uppQD3AnEpAL0S0z_WZ5jRE2-+ia6iGyuQ@mail.gmail.com>
First of all:
Hans, Devin thank you for working on this stuff !
Am 04.01.2013 21:59, schrieb Devin Heitmueller:
> On Fri, Jan 4, 2013 at 2:59 PM, Ezequiel Garcia <elezegarcia@gmail.com> wrote:
>> Maybe I'm wrong, but weren't **all** changes supposed to be sent as a PATCH
>> to the mailing list for community review, before the PULL request was sent?
> No, you are correct. I did a PULL specifically because Mauro asked me
> to.
Interesting. Can you shed some light on whats going on behind the scenes
? ;)
How does this "request for pull-request" thing work and shouldn't this
happen on the public ML, too ?
> I'll resend the individual patches now to the list.
Do you still want me to review/test it ?
I'm willing to invest some time for it, but as there is already a pull
request, it seems to be ready and I really don't want to waste my time... !?
Regards,
Frank
> Devin
>
next prev parent reply other threads:[~2013-01-05 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 19:41 [GIT PULL FOR 3.9] em28xx videobuf2 support and v4l2-compliance fixes Devin Heitmueller
2013-01-04 19:59 ` Ezequiel Garcia
2013-01-04 20:59 ` Devin Heitmueller
2013-01-05 12:49 ` Frank Schäfer [this message]
2013-01-05 12:51 ` Frank Schäfer
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=50E82165.1000100@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=dheitmueller@kernellabs.com \
--cc=elezegarcia@gmail.com \
--cc=hverkuil@xs4all.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.