Mike Vermeulen wrote:
> > This is possibly not copyrightable, but didn't you get the message - 
> > It's probably best for Open64 to not import PathScale code (regardless 
> > if it's license compatible)
>
> Christopher,
>
>
> One can read from your statement "didn't you get the message"
> an implication that somehow there is something new or different
> here.
Please don't be so dense - If you have a test case and it's so trivial 
then just debug and fix the problem.  Really what's the time/cost 
difference between isolating some small fix like this from the 3.3 
tarball vs just fixing it?

The greater point I was trying to make is both projects can collaborate 
if a sincere effort is made to resolve blocking issues. (political or 
otherwise)

Open64/AMD can cherry pick 1 bug fix at a time from a 2 year old tarball 
or collaborate and get a hundreds....


------------------------------------------------------------------------------
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
_______________________________________________
Open64-devel mailing list
Open64-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open64-devel

Reply via email to