<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000001">
<br>
<div class="moz-cite-prefix">On 11/17/2013 5:29 AM, Paul Harrison
wrote:<br>
</div>
<blockquote cite="mid:5288A87C.10701@sky.com" type="cite">On
17/11/13 10:17, John Pilkington wrote:
<br>
<blockquote type="cite">
<br>
However, I have a confession to make. My instructions for
patching mythburn.py were incomplete; they didn't follow RW's
patch. Try that.
<br>
<br>
<a class="moz-txt-link-freetext" href="http://code.mythtv.org/trac/ticket/11758#comment:2">http://code.mythtv.org/trac/ticket/11758#comment:2</a>
<br>
<br>
</blockquote>
<br>
I've committed the patch to both master and fixes to make it
easier to test.
<br>
<br>
Please report back if it fixed the problem for you.<br>
</blockquote>
I don't understand exactly, the commit system. Is it possible to
briefly explain to a novice how to figure out when this commit will
show up in my particular distribution?<br>
I'm currently running v0.27-89-g4ca9300 Branch: fixes/0.27. I
have looked at the ticket and see the extremely long commit number
as well at the changeset number, but I don't know how to follow
those numbers down to what release they first show up in.<br>
<br>
If this is beyond the scope of explaining to a novice, I understand.<br>
Thanks,<br>
Ziggy<br>
</body>
</html>