This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: upcoming glibc 2.9 - i486 problem
- From: "Ryan Arnold" <ryan dot arnold at gmail dot com>
- To: "Mike Frysinger" <vapier at gentoo dot org>, "Arkadiusz Miskiewicz" <arekm at maven dot pl>
- Cc: libc-help at sourceware dot org
- Date: Mon, 17 Nov 2008 13:09:14 -0600
- Subject: Re: upcoming glibc 2.9 - i486 problem
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=hPjqanv8jXx7nGCm2pA//HDbYhEdLRp2MDqv6N7KhU0=; b=fQ1bNTDliteerxBWzMvhe9vPq1fn79YO+20cvMBqFqWVqc/MPN4MZvMRXOT4cyTuoV wbvr2Xe6do0jbYm5IHm6WYNf5LTded5uzvk8hD9pNUPRy8xftLxzBoQYK6yhIS2Lsknp zjO8r5xc+h+M7s7GWDWa5tR7NiW2Aex0d2VAY=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=mLI5vEqxBxaEsi7Lh6HOLCJqOZfShr4go/7Bha35oo94RxUp3WviWzIuP8qhuXheOi Qx/0jM+PlEwQblvrW+/9iu2s8Nq8050gw5OyGuq1vMiugqqigxRQBB38rzx0hCurqsAF s64X3w4lf41D4mbGhz0tmmjppoLyEJckTPXqQ=
- References: <200811151149.31268.arekm@maven.pl> <200811171311.18271.vapier@gentoo.org> <ff4da150811171014i612ef604x7179f956a0edef36@mail.gmail.com> <200811171348.36072.vapier@gentoo.org>
On Mon, Nov 17, 2008 at 12:48 PM, Mike Frysinger <vapier@gentoo.org> wrote:
>> Mike, it's perfectly fine for him to come up with the patch here on
>> libc-help and then we can suggest the steps necessary for him to get
>> it to libc-alpha, including (as you mentioned) a proper ChangeLog.
>
> i didnt say you cant send patches on libc-help. i was telling him the next
> step to get things merged: post to libc-alpha.
Sorry for the misunderstanding.
> the checklist is probably a better 'next' step before libc-alpha, thanks.
Arkadisuz, it's your patch. You should submit it. since it isn't
'significant' you won't need FSF copyright assignment, but other than
that please follow the steps as indicated here:
http://sources.redhat.com/glibc/wiki/Contribution%20checklist
Ryan S. Arnold