unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: Failing misc/check-installed-headers-c with new kernel headers.
Date: Wed, 16 Jan 2019 16:23:52 -0500	[thread overview]
Message-ID: <xn1s5cjnyv.fsf@greed.delorie.com> (raw)
In-Reply-To: <30a12210-dbcc-f92f-ad59-2b1c5ad10136@redhat.com> (carlos@redhat.com)


I think ignoring comments is the right way to go, else we can't allow a
comment like:

  /* Don't use ulong here, it's obsolete.  */

I don't ever think it's a good idea for commentary to limit technical
choice.

I won't comment on how hard expanding a regex might be ;-)

  parent reply	other threads:[~2019-01-16 21:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 21:10 Failing misc/check-installed-headers-c with new kernel headers Carlos O'Donell
2019-01-16 21:21 ` Florian Weimer
2019-01-17  2:49   ` Carlos O'Donell
2019-01-18 10:15     ` Florian Weimer
2019-01-16 21:23 ` DJ Delorie [this message]
2019-01-16 23:05   ` [RFC] Ignore source code comments in scripts/check-installed-headers.sh Tulio Magno Quites Machado Filho
2019-01-16 23:15     ` DJ Delorie
2019-01-16 23:22       ` Tulio Magno Quites Machado Filho
2019-01-16 23:29         ` DJ Delorie
2019-01-17  0:14           ` Tulio Magno Quites Machado Filho
2019-01-17 10:06             ` Szabolcs Nagy
2019-01-17 10:09               ` Szabolcs Nagy
2019-01-19 16:44 ` Failing misc/check-installed-headers-c with new kernel headers 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

  List information: https://www.gnu.org/software/libc/involved.html

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

  git send-email \
    --in-reply-to=xn1s5cjnyv.fsf@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.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).