Re: Legal paperwork for GCC contributions

2014-12-23 Thread Lawrence Velázquez
On Dec 22, 2014, at 9:54 PM, Lawrence Velázquez wrote: > On Dec 6, 2014, at 8:01 PM, Lawrence Velázquez wrote: > >> On Nov 23, 2014, at 6:48 PM, Lawrence Velázquez wrote: >> >>> I recently contributed some fixes against GCC trunk, gcc-4_9-branch, and >>>

Re: Legal paperwork for GCC contributions

2014-12-22 Thread Lawrence Velázquez
On Dec 6, 2014, at 8:01 PM, Lawrence Velázquez wrote: > On Nov 23, 2014, at 6:48 PM, Lawrence Velázquez wrote: > >> I recently contributed some fixes against GCC trunk, gcc-4_9-branch, and >> gcc-4_8-branch for which I need the requisite legal paperwork. > > Ping? Ping? Part II vq

Re: Legal paperwork for GCC contributions

2014-12-06 Thread Lawrence Velázquez
On Nov 23, 2014, at 6:48 PM, Lawrence Velázquez wrote: > I recently contributed some fixes against GCC trunk, gcc-4_9-branch, and > gcc-4_8-branch for which I need the requisite legal paperwork. Ping? vq

Re: Legal paperwork for GCC contributions

2014-11-23 Thread Lawrence Velázquez
On Nov 23, 2014, at 8:14 PM, Jack Howarth wrote: > Is this even an issue considering that MacPorts is only applying these fixes > as patches on final source releases of the Apple GCC 4.2 and LLVM-GCC 4.2 > compilers and there is zero chance of those ever making their way into an > actively mai

Legal paperwork for GCC contributions

2014-11-23 Thread Lawrence Velázquez
Hi, I recently contributed some fixes against GCC trunk, gcc-4_9-branch, and gcc-4_8-branch for which I need the requisite legal paperwork. However, I'd like to backport these particular fixes to the MacPorts Project's ports of Apple GCC 4.2 and LLVM-GCC 4.2, which are licensed under "version 2,