From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 49982 invoked by alias); 18 Jan 2018 14:22:20 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 49971 invoked by uid 89); 18 Jan 2018 14:22:19 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=intentions, gr, promised, our X-HELO: relay1.mentorg.com From: Thomas Schwinge To: Samuel Thibault CC: Florian Weimer , , GNU C Library , Joseph Myers Subject: Re: Upstreaming the glibc Hurd port In-Reply-To: <20180118135758.xqla2yevcrjjk7si@var.youpi.perso.aquilenet.fr> References: <20180118124537.yampmyfjsbi6wvia@var.youpi.perso.aquilenet.fr> <20180118135758.xqla2yevcrjjk7si@var.youpi.perso.aquilenet.fr> User-Agent: Notmuch/0.9-101-g81dad07 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Thu, 18 Jan 2018 14:22:00 -0000 Message-ID: <87mv1btffy.fsf@hertz.schwinge.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-SW-Source: 2018-01/txt/msg00607.txt.bz2 Hi! Despite my good intentions, in the past year (or even longer...) I failed to allocate sufficient time to do any substantial work on the Hurd side, but I'll now allocate time to at least help with... On Thu, 18 Jan 2018 14:57:58 +0100, Samuel Thibault wrote: > Joseph Myers, on jeu. 18 janv. 2018 13:47:42 +0000, wrote: > > All the usual coding standards of course apply, >=20 > And that's were I haven't received help so far. ... that. (Plus the GDB stuff I promised to look into.) > I can pile-commit what we currently have, with all the XXXs, FIXMEs, > etc., if that can help the glibc side. I'm not sure if that's a useful thing to spend time on, right now. I think it'll be better if we first integrate into glibc upstream the changes that are non-controversial on our own side, which only touch Hurd code, etc. Then, for the rest of the changes, those which also touch generic glibc code, we should then discuss these individually. > But the actual discussion of changes is what takes time, and bug-hurd > people have to actually help me with it (or at least unload from me the > coding standards and ChangeLog parts) if they want it to happen fast > enough. ACK. Gr=C3=BC=C3=9Fe Thomas