On 4/18/07, <b class="gmail_sendername">Axel Thimm</b> <<a href="mailto:Axel.Thimm@atrpms.net">Axel.Thimm@atrpms.net</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>> What about atrpms-bleeding? It mentions trunk_r13228, but I see<br>> they are up to 13276 as of a few minutes ago. How often is the<br>> mythtv in bleeding rebuilt?<br><br>* Fri Apr 13 2007 Axel Thimm <
<a href="mailto:Axel.Thimm@ATrpms.net">Axel.Thimm@ATrpms.net</a>> - 0.21-118_trunk_r13228<br>- Update to latest svn trunk (13228).<br><br>So the packages are less than a week old.</blockquote><div><br>Sounds good. Thanks for the info and I appreciate your work on the repo. You confirmed that bleeding does not perform a nightly build of Myth SVN. :)
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> What is the best way for me to figure out what firewire improvements<br>> are in trunk that have not been back-ported to
0.20-fixes?<br><br>That's difficult, it requires to check the commit logs, or ask the<br>respective subsystem maintainer.</blockquote><div><br>I searched Myth TRAC for firewire and learned a little about the mythtv-firewire branch. It appears most of the fixes were merged to trunk in January.
<br><br>/Brian/<br></div></div>