From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 63249 invoked by alias); 18 Jan 2018 12:45:49 -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 63078 invoked by uid 89); 18 Jan 2018 12:45:45 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL autolearn=no version=3.3.2 spammy=H*r:sk:AES256-, activities X-HELO: mail3-relais-sop.national.inria.fr Date: Thu, 18 Jan 2018 12:45:00 -0000 From: Samuel Thibault To: Florian Weimer , bug-hurd@gnu.org Cc: Thomas Schwinge , GNU C Library Subject: Re: Upstreaming the glibc Hurd port Message-ID: <20180118124537.yampmyfjsbi6wvia@var.youpi.perso.aquilenet.fr> Mail-Followup-To: Florian Weimer , bug-hurd@gnu.org, Thomas Schwinge , GNU C Library References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) X-SW-Source: 2018-01/txt/msg00596.txt.bz2 Florian Weimer, on jeu. 18 janv. 2018 13:39:51 +0100, wrote: > Is it just a matter of someone doing the work of upstreaming all the > existing patches? It's mostly that, yes. > If we cannot resolve this is in the coming months, I think we should > seriously consider a removal of the Hurd port, I'm afraid. Ok, then I can take the time to do it, but as usual it'll be at the expense of other Hurd activities, e.g. the obvious Meltdown/Spectre issues, etc. Unless bug-hurd people actually help me with it. Samuel