Stop forking around<br><br><div class="gmail_quote">On Thu, Jan 27, 2011 at 9:57 PM, drew Roberts <span dir="ltr">&lt;<a href="mailto:zotz@100jamz.com">zotz@100jamz.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
On Thursday 27 January 2011 11:56:22 Paul Davis wrote:<br>
&gt; i just don&#39;t remember other cases where major existing FLOSS projects<br>
&gt; were forked<br>
<br>
This is not about what is going in in this thread in any direct way. (Or may<br>
not be at least, I do not know enough to say I guess.)<br>
<br>
What if I &quot;fork&quot; a project because I think it gives me a good starting point<br>
or base for what I want to do but the direction I intend to take things will<br>
result in a completely different sort of program to the one I forked? Should<br>
that still be considered a fork or is there another term for such a beast?<br>
Would another term be useful?<br>
<br>
all the best,<br>
<br>
drew<br>
_______________________________________________<br>
Linux-audio-dev mailing list<br>
<a href="mailto:Linux-audio-dev@lists.linuxaudio.org">Linux-audio-dev@lists.linuxaudio.org</a><br>
<a href="http://lists.linuxaudio.org/listinfo/linux-audio-dev" target="_blank">http://lists.linuxaudio.org/listinfo/linux-audio-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><span style="clear: both;">&quot;Cheshire-Puss,&quot; she began, &quot;would you tell me, please,<br>
		which way I ought to go from here?&quot;<br>
&quot;That depends a good deal on where you want to get to,&quot; said the Cat.<br>
&quot;I don&#39;t care much where--&quot; said Alice.<br>
&quot;Then it doesn&#39;t matter which way you go,&quot; said the Cat.</span><br><br>