<html><head></head><body><br>
While this may be so for a number of patches, my personal experience has been somewhat different with responses most of the time having nothing to do with the patch at hand (if I got any in the first place). I imagine if a patch is declined one would expect it being reported as such with an explanation as to what is the reason for such decision, and ideally with a response that actually makes sense so that an appropriate improvement can be made.<br>
<br>
Similarly, while I fully understand that reviewing patches can be quite time consuming, please do not forget that fixing a bug and creating a report in the patch tracker together with supporting documentation can be doubly so.<br>
<br>
Ivica Ico Bukvic, D.M.A<br>
Composition, Music Technology<br>
Director, DISIS Interactive Sound & Intermedia Studio<br>
Director, L2Ork LinuxLaptop Orchestra<br>
Assistant Co-Director, CCTAD<br>
CHCI, CS, and Art (by courtesy)<br>
Virginia Tech<br>
Department of Music<br>
Blacksburg, VA 24061-0240<br>
(540) 231-6139<br>
(540) 231-5034 (fax)<br>
<a href="http://disis.music.vt.edu">disis.music.vt.edu</a><br>
<a href="http://l2ork.music.vt.edu">l2ork.music.vt.edu</a><br>
<a href="http://ico.bukvic.net">ico.bukvic.net</a><br><br><div class="gmail_quote">Hans-Christoph Steiner <hans@at.or.at> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif"><br />On Thu, 07 Jul 2011 16:39 +0200, "Ivica Ico Bukvic" <ico@vt.edu> wrote:<br />> > I ended up refactoring the magic glass and highlighting code quite a<br />> > bit, I think there might be something worth checking out. As for<br />> > other bug fixes, it would be great to have them in the patch tracker<br />> > so we can sort them out. It would take me a massive amount of time to<br />> > figure out what code changes are for what in pdl2ork since there isn't<br />> > any version control (that I could find at least) and it seems to be a<br />> > mix of 0.42 and 0.43 versions.<br />> <br />> It's based off of 0.42.6 extended tree. As for submitting patches, I've<br />> been doing this in the past. Alas, a good number of them never got any<br />> attention which is not very encouraging.<br /><br />If you look at the patch tracker, a!
nd
filter on Closed ones, you'll see<br />which ones get accepted. Most do. It takes a lot of time to review<br />patches, so if they don't cleanly apply and build, then I'm not really<br />likely to pursue it much further. I've tried figuring out patches like<br />that in the past, and it just takes too much time to try to figure out<br />what's wrong, etc. and it doesn't speak well of the patch if it doesn't<br />past the first hurdle.<br /><br />.hc<br /></pre></blockquote></div></body></html>