From: Michael Matz <matz@suse.de>
To: Mark Wielaard <mark@klomp.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, gnu-gabi@sourceware.org
Subject: Re: Document existing GNU extensions
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1602221445430.20277@wotan.suse.de> (raw)
In-Reply-To: <20160219225240.GF2586@blokker.redhat.com>
Hi,
On Fri, 19 Feb 2016, Mark Wielaard wrote:
> Not yet. But we should get one once we have concensus about how to make
> sure we document things.
>
> I hope we can do it with minimal rules, just discuss any proposals to
> document things on this list till there is concensus on the wording.
>
> I propose we invite the global maintainers of each of the GNU toolchain
> projects (gcc, gdb, binutils and glibc)
The global maintainers of at least GCC is a fuzzy definition ...
> to appoint one reviewer/approver who is responsible for making sure
... and I think anyone interested in ABIs should meanwhile be aware of the
existence of this list.
> anything we document is actually a stable GNU gabi extension they are
> willing to support (and not some accidental mistake that might seem to
> work, but was never intented as public abi). Their job would simply be
> to say "yes", "no" or "please, refer to another standard or project
> documentation as official source" about any text we come up with that
> has concensus. That way we make sure that what we document is actually
> supported by the GNU toolchain projects for others to rely on.
Well, as many of the things H.J. listed are effectively part of the
dynamic linker/library/application contract they _are_ part of the ABI,
and better be supportable for basically forever. So documenting existing
behaviour, no matter if intended or accidental, seems worthwhile
independend of anyone actually agreeing that the extension as is is
"fine".
That's of course different with any new proposed extensions.
Ciao,
Michael.
prev parent reply other threads:[~2016-02-22 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 H.J. Lu
2016-01-01 0:00 ` Mark Wielaard
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` Michael Matz [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=alpine.LSU.2.20.1602221445430.20277@wotan.suse.de \
--to=matz@suse.de \
--cc=gnu-gabi@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=mark@klomp.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).