This is the mail archive of the libc-ports@sources.redhat.com mailing list for the libc-ports project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: glibc alpha patches


On Fri, Jan 16, 2009 at 02:14:43PM -0500, Mike Frysinger wrote:
> i have one via work for Blackfin work, but i dont think that covers glibc and 
> i think it may only be for stuff that i can say is for Blackfin work ?  
> writing patches for alpha clearly doesnt fall into that category :)

You'd have to check with the FSF or your employer for details about whether it was
restricted to Blackfin.  In this case I can verify that it doesn't
cover glibc (assuming we're talking about Analog Devices here);
there's assignments for about everything else under the sun, but not
GLIBC.

Some patches can fit "under the wire", as it were, and this one is
tiny so ought to be fine anyway.

> i certainly dont claim to be an alpha expert, but i have access to alpha 
> hardware (personal and through Gentoo) and there are people in Gentoo i can 
> bounce questions off of.  your reluctance is certainly understandable, but the 
> alpha port as it stands today is already broken and needs patches to build let 
> alone actually run properly.  (dont take that statement to mean i think you 
> should be committing these patches because you have write access ... i'm just 
> reiterating the facts)

Right, I acknowledge all of the above as true.  I don't have a big
problem committing patches tested by Gentoo (or Debian, etc),
especially for otherwise broken ports - mostly I just don't have the
time to sanity check them.

-- 
Daniel Jacobowitz
CodeSourcery


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]