From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 55511 invoked by alias); 18 Jan 2018 15:14:52 -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 55501 invoked by uid 89); 18 Jan 2018 15:14:51 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL autolearn=no version=3.3.2 spammy=H*r:sk:AES256- X-HELO: mail3-relais-sop.national.inria.fr Date: Thu, 18 Jan 2018 15:14:00 -0000 From: Samuel Thibault To: Thomas Schwinge Cc: Florian Weimer , bug-hurd@gnu.org, GNU C Library , Joseph Myers Subject: Re: Upstreaming the glibc Hurd port Message-ID: <20180118151446.zqlmpbmgg4kvs2y3@var.youpi.perso.aquilenet.fr> Mail-Followup-To: Thomas Schwinge , Florian Weimer , bug-hurd@gnu.org, GNU C Library , Joseph Myers References: <20180118124537.yampmyfjsbi6wvia@var.youpi.perso.aquilenet.fr> <20180118135758.xqla2yevcrjjk7si@var.youpi.perso.aquilenet.fr> <87mv1btffy.fsf@hertz.schwinge.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87mv1btffy.fsf@hertz.schwinge.homeip.net> User-Agent: NeoMutt/20170113 (1.7.2) X-SW-Source: 2018-01/txt/msg00611.txt.bz2 Thomas Schwinge, on jeu. 18 janv. 2018 15:22:09 +0100, wrote: > 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, > > > > And that's were I haven't received help so far. > > ... that. (Plus the GDB stuff I promised to look into.) Well, cool, but I'd prefer that you spend your available time on the gdb things and the *content* of the glibc patches which we need :) (for some of the patches in mentioned in a separate mail, there is no real explanation why they are needed, what should be done about them, etc.) Coding standards can be worked on by anybody, this is really something that bug-hurd people can unload us from. Samuel