<font face="trebuchet ms,sans-serif">Can anyone clarify my doubt, please?</font><div><font face="trebuchet ms,sans-serif">In other words, the main point is: can different branches of the same package host different forks of a software?</font></div>
<div><font face="trebuchet ms,sans-serif">Thanks.</font></div><div><br><div class="gmail_quote">2012/10/21 M.M. <span dir="ltr"><<a href="mailto:hal8600@hotmail.it" target="_blank">hal8600@hotmail.it</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font face="trebuchet ms,sans-serif">Thanks, but my question is: is it enough to just package the new fork into the F-18 and devel branches and leave the previous ones unchanged and out-of date? <br>
</font><div class="HOEnZb"><div class="h5"><br><div class="gmail_quote">
2012/10/20 Ken Dreyer <span dir="ltr"><<a href="mailto:ktdreyer@ktdreyer.com" target="_blank">ktdreyer@ktdreyer.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Sat, Oct 20, 2012 at 1:59 PM, M.M. <<a href="mailto:hal8600@hotmail.it" target="_blank">hal8600@hotmail.it</a>> wrote:<br>
> branches only and simply leaving the F-16 and F-17 branches unchanged.<br>
> Is this the right approach? If not, how should I behave?<br>
<br>
</div>Has Neroth given up development on his version forever? If so, it<br>
sounds sensible to me to switch in RPM Fusion.<br>
<span><font color="#888888"><br>
- Ken<br>
<br>
</font></span></blockquote></div><br>
</div></div></blockquote></div><br></div>