From: Andreas Schwab <schwab@suse.de>
To: Zack Weinberg <zackw@panix.com>
Cc: libc-alpha@sourceware.org, fweimer@redhat.com, joseph@codesourcery.com
Subject: Re: [PATCH v2 2/2] Don't include libio.h from stdio.h.
Date: Tue, 02 Jan 2018 09:37:00 -0000 [thread overview]
Message-ID: <mvm8tdgha9f.fsf@suse.de> (raw)
In-Reply-To: <20180102034436.11037-2-zackw@panix.com> (Zack Weinberg's message of "Mon, 1 Jan 2018 22:44:36 -0500")
On Jan 01 2018, Zack Weinberg <zackw@panix.com> wrote:
> diff --git a/libio/bits/types/struct_FILE.h b/libio/bits/types/struct_FILE.h
> new file mode 100644
> index 0000000000..a7598886f4
> --- /dev/null
> +++ b/libio/bits/types/struct_FILE.h
> @@ -0,0 +1,103 @@
> +#ifndef __struct_FILE_defined
> +#define __struct_FILE_defined 1
> +
> +/* Caution: The contents of this file are not part of the official
> + stdio.h API. However, much of it is part of the official *binary*
> + interface, and therefore cannot be changed. */
> +
Missing copyright header.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2018-01-02 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 3:44 [PATCH v2 1/2] Avoid using libio internal symbols outside libio & stdio-common Zack Weinberg
2018-01-02 3:44 ` [PATCH v2 2/2] Don't include libio.h from stdio.h Zack Weinberg
2018-01-02 9:37 ` Andreas Schwab [this message]
2018-01-08 12:46 ` Zack Weinberg
2018-01-08 12:45 ` [PATCH v2 1/2] Avoid using libio internal symbols outside libio & stdio-common Zack Weinberg
2018-01-08 14:36 ` Florian Weimer
2018-01-08 15:35 ` Zack Weinberg
2018-01-08 15:40 ` Florian Weimer
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=mvm8tdgha9f.fsf@suse.de \
--to=schwab@suse.de \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=zackw@panix.com \
/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).