public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [hurd,commited] hurd: do not check Mach and Hurd headers
Date: Sun, 04 Mar 2018 01:46:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.20.1803040144320.17758@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20180304014350.wjc7itlnk4jisjzc@var.youpi.perso.aquilenet.fr>

On Sun, 4 Mar 2018, Samuel Thibault wrote:

> Joseph Myers, on dim. 04 mars 2018 01:41:43 +0000, wrote:
> > My reading of <https://sourceware.org/ml/libc-alpha/2018-03/msg00074.html> 
> > is that it still has:
> > 
> > +        # Hurd headers are not standard anyway
> > +        (hurd.h | hurd/*.h | faultexc_server.h)
> > +            continue;;
> 
> The reading of the patch really is all the - on mach headers.  Small
> step to get something done instead of having to do _*ALL*_ the work at
> one time and never manage to find motivation to finish it all.

I don't actually see the problem with having some of these tests failing - 
no Hurd special cases in this script - unless and until we decide that a 
particular Hurd special case in this script is appropriate.  That was how 
we handled many architecture-specific fixes for header problems shown by 
these tests for GNU/Linux (some of these tests failed on some 
architectures for some time); I think it's how we should handle them for 
Hurd.  When individual headers are fixed, the number of failures may go 
down.

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2018-03-04  1:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-03 19:18 Samuel Thibault
2018-03-03 22:08 ` Joseph Myers
2018-03-03 22:32   ` Samuel Thibault
2018-03-03 22:53     ` Joseph Myers
2018-03-03 23:57       ` Samuel Thibault
2018-03-04  1:33         ` Joseph Myers
2018-03-04  1:35           ` Samuel Thibault
2018-03-04  1:41             ` Joseph Myers
2018-03-04  1:43               ` Samuel Thibault
2018-03-04  1:46                 ` Joseph Myers [this message]
2018-03-04  1:46               ` Samuel Thibault
2018-03-04  0:32       ` Samuel Thibault
2018-03-04  1:28         ` Joseph Myers
2018-03-04  2:55       ` Samuel Thibault
2018-03-04 16:08         ` Zack Weinberg
2018-03-04 18:10           ` Samuel Thibault
2018-03-05  0:30             ` Zack Weinberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.20.1803040144320.17758@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=samuel.thibault@ens-lyon.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).