From: david.hagood@gmail.com
To: "Roger" <rogerx.oss@gmail.com>
Cc: unlisted-recipients:; ""@Deathwish.hagood.sktc.net,
"no To-header on input"
<"@yx-in-f108.1e100.net"@Deathwish.hagood.sktc.net>,
linux-media@vger.kernel.org
Subject: Re: dvbscan output Channel Number into final stdout?
Date: Fri, 30 Sep 2011 12:34:41 -0500 [thread overview]
Message-ID: <e9f9d962fccf0ef7c4bddd24ed065c8c.squirrel@localhost> (raw)
In-Reply-To: <20110930080609.GD2284@localhost2.local>
Even that won't always save you. In my area, we have 2 distinct signals,
both identifying themselves as "KAKE-DT" on virtual channel 10.1, so even
that isn't guaranteed to be unique.
next prev parent reply other threads:[~2011-09-30 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 22:44 dvbscan output Channel Number into final stdout? Roger
2011-09-30 7:17 ` tvboxspy
2011-09-30 8:06 ` Roger
2011-09-30 17:34 ` david.hagood [this message]
2011-09-30 20:53 ` Roger
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=e9f9d962fccf0ef7c4bddd24ed065c8c.squirrel@localhost \
--to=david.hagood@gmail.com \
--cc=rogerx.oss@gmail.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