From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PULL] soc-camera 3.7 set 2
Date: Sat, 6 Oct 2012 09:10:26 -0300 [thread overview]
Message-ID: <20121006091026.14970663@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1209111107340.22084@axis700.grange>
Hi Guennadi,
Em Tue, 11 Sep 2012 11:08:58 +0200 (CEST)
Guennadi Liakhovetski <g.liakhovetski@gmx.de> escreveu:
> Hi Mauro
>
> The following changes since commit 79e8c7bebb467bbc3f2514d75bba669a3f354324:
Next time, please use "[GIT PULL]" for the subject; I seek for _git_ string
for the patch name on my queue during the merge windows, in order to speedup
patches from driver maintainers when I got overloaded.
This is the case of this merge window: I still have ~270 patches (or pull requests)
to handle, and this is already our record in terms of number of patches:
~720 patches already sent, and there are already 67 new patches for the
second part.
Thanks!
Mauro
prev parent reply other threads:[~2012-10-06 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 9:08 [PULL] soc-camera 3.7 set 2 Guennadi Liakhovetski
2012-10-06 12:10 ` 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=20121006091026.14970663@redhat.com \
--to=mchehab@redhat.com \
--cc=g.liakhovetski@gmx.de \
--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;
as well as URLs for NNTP newsgroup(s).