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: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: "Mike Frysinger" <vapier at gentoo dot org>
- Cc: "Ryan Arnold" <ryan dot arnold at gmail dot com>, "Arkadiusz Miskiewicz" <arekm at maven dot pl>, libc-help at sourceware dot org
- Date: Mon, 17 Nov 2008 15:31:54 -0500
- 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:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=d5M9CU7a0Nk43Z6gbvFxeWicwutozaFUJrzbLBEqeJQ=; b=YSYRt09eleUZZQO4VI+N0qVdfOUlNNHW7Ik3NfNPA0TZk5oOrk89ahW3BCYJMYKWeD euzDQwFJX4xHpm0lTFS7tBBXkZ0eROGkiTo26fdANTT9H4+Rpqtx23+ot4AXy7cqaY5T bW2MqEzNKBUuyXiIDsKpr4vasI4Yhe58blYiQ=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=fv1kN1TKSs9UXIWyzFzqWxfa8sKoW+lmWYfALze+IcgAR5pxqmnwMP+q+AKuCoi6hy ypB/6ecPUhRedz7L+q0VBVq5U2DpHYI95oiSlUCix2qORalry4tjWymgiSe02tA+I868 Yh9f5b3DCKS4NuJSiz3UFQ58kvxGGyOTJpHo8=
- References: <200811151149.31268.arekm@maven.pl> <200811171348.36072.vapier@gentoo.org> <ff4da150811171109t2c320fceu5023092408ce6396@mail.gmail.com> <200811171454.06063.vapier@gentoo.org>
On Mon, Nov 17, 2008 at 2:54 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> On Monday 17 November 2008 14:09:14 Ryan Arnold wrote:
>> 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.
>
> np. i wonder if a more "guiding hand" document would be good to have ? we
> have the checklist, but that requires a bit of knowledge to get there ... or
> maybe just an intro on the checklist document that says "feel free to ask for
> help on the libc-help mailing list" ?
The checklist is on the wiki, please add whatever you think is missing.
We trust you Mike :-)
Cheers,
Carlos.