From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: linuxtv-commits@linuxtv.org
Cc: linux-media@vger.kernel.org, mchehab@s-opensource.com
Subject: Re: [git:media_tree/master] foo
Date: Tue, 20 Jun 2017 10:34:54 -0300 [thread overview]
Message-ID: <20170620103454.3c80ed17@vento.lan> (raw)
In-Reply-To: <E1dNHGh-0002VG-7X@www.linuxtv.org>
Em Tue, 20 Jun 2017 11:19:56 +0000
Mauro Carvalho Chehab <mchehab@s-opensource.com> escreveu:
> This is an automatic generated email to let you know that the following patch were queued:
>
> Subject: foo
> Author: Mauro Carvalho Chehab <mchehab@s-opensource.com>
> Date: Tue Jun 20 08:19:56 2017 -0300
This one was just to see if people are paying atention...
It turns that people were, as I got two reports already
about it! :-D
Seriously, I was doing a test with gcc warnings, before writing a
real fix for double const.
Once I noticed I merged it by mistake, I folded it with the right
fix and rebased, before applying other patches at the tree. So,
hopefully, no harm done (except that sfr pulled from my tree on
that time, so, we may have some noise on today's -next).
Thanks,
Mauro
parent reply other threads:[~2017-06-20 13:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1dNHGh-0002VG-7X@www.linuxtv.org>]
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=20170620103454.3c80ed17@vento.lan \
--to=mchehab@s-opensource.com \
--cc=linux-media@vger.kernel.org \
--cc=linuxtv-commits@linuxtv.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).