<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font color="#3366ff">I don't want to act like a smug idiot...</font></blockquote><div>
You are. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font color="#3366ff"> but I like my version of the<br>
patch better for (at least) 2 reasons:</font></blockquote><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font color="#3366ff">
1. The original patch modifications (hack_out_ogg.diff) made by my patch<br>
no longer use "relative" paths (i.e. "../../") and thus comply with any<br>
version of the patch used.<br></font></blockquote><div>Move to the JIRA. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font color="#3366ff">
2. My modifications made to the appropriate mod_shout Makefile are much<br>
better, because they use SHOUT_BUILDDIR, which is already defined in<br>
that Makefile, and do not rely on some hard-coded path ("../../../../"<br>
for example). In other words, I think:<br></font></blockquote><div>Move to the JIRA. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font color="#3366ff">
patch -d $(SHOUT_BUILDDIR) -p1 < hack_out_ogg.diff (which is what my<br>
patch proposes) is much better than:<br>
patch -p 6 -d ../../../../libs/libshout-2.2.2 < hack_out_ogg.diff (which<br>
is what Alexsey have proposed)</font></blockquote><div>Move to the JIRA. Seriously. This has already been mentioned several times. This stuff DOES NOT BELONG HERE. Bugs are to be reported in one place, <a href="http://jira.freeswitch.org">http://jira.freeswitch.org</a>. That's it. No if's. and's, or but's. You're complaining that the developers are ignoring you, and at the same time you are making it HARDER for them to help you by posting information in two (possibly more) different places. Seems like there's already duplicate bug reports for this, those probably need to be merged as well.</div>
<div><br></div><div>Move to the JIRA.</div><div><br></div><div>-BDF </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<br>
<br>
_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
<a href="http://www.cudatel.com" target="_blank">http://www.cudatel.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://wiki.freeswitch.org" target="_blank">http://wiki.freeswitch.org</a><br>
<a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br><br>This message contains confidential information and is intended for those listed in the "To:", "CC:", and/or "BCC:" fields of the message header.If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.<br>
<br>