From: Jeff Johnston <jjohnstn@redhat.com>
To: Yaakov Selkowitz <yselkowitz@cygwin.com>
Cc: Newlib <newlib@sourceware.org>
Subject: Re: [PATCH v2 00/17] Newlib ANSI-fication
Date: Wed, 17 Jan 2018 15:58:00 -0000 [thread overview]
Message-ID: <CAOox84s6bYWdHLnDr_77wbPg64aadpS_N0YLKgKtOHFW4rq+Rg@mail.gmail.com> (raw)
In-Reply-To: <77e4dc73-6701-bf5d-ef1c-631744718b9a@cygwin.com>
I already mentioned I would do the docs if you checked in the patches. It
would be a simple
statement to say that K&R support used to exist but was removed as of 3.0.
As well, there
is a section on more documentation and you can state that docs used to have
multiple formats
supported, but no longer. Anyway, as I said, I will do the docs as part
of the 3.0 snapshot.
-- Jeff J.
On Tue, Jan 16, 2018 at 9:49 PM, Yaakov Selkowitz <yselkowitz@cygwin.com>
wrote:
> On 2018-01-10 09:58, Yaakov Selkowitz wrote:
> > On 2017-12-18 16:29, Jeff Johnston wrote:
> >> ACK as well, but please add some documentation.
> >
> > Where, exactly?
>
> newlib/README already says the following since at least 2000:
>
> NOTE THAT YOU MUST HAVE ALREADY BUILT AND INSTALLED GCC and BINUTILS.
>
> Which would already rule out any ancient or custom K&R compilers, so I'm
> really not sure if and how to further specify this.
>
> --
> Yaakov
>
>
prev parent reply other threads:[~2018-01-17 15:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 18:19 Yaakov Selkowitz
2017-12-07 18:19 ` [PATCH v2 04/17] ansification: remove _NOARGS Yaakov Selkowitz
2017-12-07 18:19 ` [PATCH v2 07/17] ansification: remove _PTR Yaakov Selkowitz
2017-12-07 18:19 ` [PATCH v2 03/17] ansification: remove _DOTS Yaakov Selkowitz
2017-12-07 18:20 ` [PATCH v2 01/17] ansification: remove _AND Yaakov Selkowitz
2017-12-07 18:20 ` [PATCH v2 14/17] ansification: remove _EXFUN, _EXFUN_NOTHROW Yaakov Selkowitz
2017-12-07 19:08 ` Craig Howland
2017-12-12 0:08 ` Yaakov Selkowitz
2017-12-07 18:20 ` [PATCH v2 13/17] ansification: remove _EXFNPTR, _EXPARM Yaakov Selkowitz
2017-12-07 18:20 ` [PATCH v2 02/17] ansification: remove _CONST Yaakov Selkowitz
2017-12-07 18:20 ` [PATCH v2 06/17] ansification: remove _VOID_PTR Yaakov Selkowitz
2017-12-07 18:26 ` [PATCH v2 09/17] ansification: remove _DEFUN_VOID Yaakov Selkowitz
2017-12-07 18:26 ` [PATCH v2 11/17] ansification: remove _VOLATILE, _SIGNED Yaakov Selkowitz
2017-12-07 18:26 ` [PATCH v2 12/17] ansification: remove _DEFUN Yaakov Selkowitz
2017-12-07 18:27 ` [PATCH v2 05/17] ansification: remove _PARAMS Yaakov Selkowitz
2017-12-07 18:28 ` [PATCH v2 10/17] ansification: remove _VOID Yaakov Selkowitz
2017-12-07 18:29 ` [PATCH v2 15/17] ansification: remove _HAVE_STDC Yaakov Selkowitz
2017-12-07 18:29 ` [PATCH v2 16/17] ansification: fix makedoc for ANSI C Yaakov Selkowitz
2017-12-07 18:29 ` [PATCH v2 08/17] ansification: remove _CAST_VOID Yaakov Selkowitz
2017-12-07 18:55 ` [PATCH v2 17/17] ansification: remove ansidecl.h from makedoc Yaakov Selkowitz
2017-12-12 12:51 ` [PATCH v2 00/17] Newlib ANSI-fication Corinna Vinschen
2017-12-19 4:50 ` Jeff Johnston
2018-01-09 14:34 ` Sebastian Huber
2018-01-18 12:35 ` Sebastian Huber
2018-01-10 15:58 ` Yaakov Selkowitz
2018-01-17 2:49 ` Yaakov Selkowitz
2018-01-17 4:42 ` [PATCH] Bump release to 3.0.0 for removal of K&R compatibility Yaakov Selkowitz
2018-01-17 15:58 ` Jeff Johnston [this message]
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=CAOox84s6bYWdHLnDr_77wbPg64aadpS_N0YLKgKtOHFW4rq+Rg@mail.gmail.com \
--to=jjohnstn@redhat.com \
--cc=newlib@sourceware.org \
--cc=yselkowitz@cygwin.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).