From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Andy Walls <awalls@md.metrocast.net>
Cc: linux-media@vger.kernel.org, linuxtv-commits@linuxtv.org,
Michael Krufky <mkrufky@kernellabs.com>
Subject: Re: [git:v4l-dvb/ivtv] V4L/DVB: tda18271: fix error detection during initialization of first instance
Date: Sat, 26 Jun 2010 10:35:42 -0300 [thread overview]
Message-ID: <4C26022E.5060008@redhat.com> (raw)
In-Reply-To: <1277558644.8545.4.camel@localhost>
Em 26-06-2010 10:24, Andy Walls escreveu:
> On Sat, 2010-06-26 at 14:51 +0200, Mauro Carvalho Chehab wrote:
>> This is an automatic generated email to let you know that the following patch were queued at the
>> http://git.linuxtv.org/v4l-dvb.git tree:
>>
>> Subject: V4L/DVB: tda18271: fix error detection during initialization of first instance
>> Author: Michael Krufky <mkrufky@kernellabs.com>
>> Date: Mon May 3 02:10:15 2010 -0300
>
> Hi Mauro,
>
> The e-mail subject line has "ivtv" in it, but no ivtv related changes in
> the email. I'm guessing this is a branch tag?
>
> Regards,
> Andy
>
Yes, I noticed only after merging upstream... Sorry for the mess.
I have a number of working dirs here, in order to handle each staging tree, but, due to disk
constraints (each working tree eats about 300Mb, plus extra space when I run make).
Unfortunately, I currently can't have a one-per-one mapping. Those patches were meant to go
to staging/other. This should cause no big deal, but I really need to buy more disks and an
extra disk case for my Dell machine. On the other hand, reverting the patches at the upstream
tree will be bad, since it may break trees from others that pull from mine.
Cheers,
Mauro
prev parent reply other threads:[~2010-06-26 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1OSV9v-0001x8-3g@www.linuxtv.org>
2010-06-26 13:24 ` [git:v4l-dvb/ivtv] V4L/DVB: tda18271: fix error detection during initialization of first instance Andy Walls
2010-06-26 13:35 ` 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=4C26022E.5060008@redhat.com \
--to=mchehab@redhat.com \
--cc=awalls@md.metrocast.net \
--cc=linux-media@vger.kernel.org \
--cc=linuxtv-commits@linuxtv.org \
--cc=mkrufky@kernellabs.com \
/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