From: Suprateeka R Hegde <hegdesmailbox@gmail.com>
To: gnu-gabi@sourceware.org
Subject: Minor updates to GNU-gABI
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <9ca4c32a-3c7c-5ec0-1eec-c3770f05c261@gmail.com> (raw)
Hi
I have a bunch of thoughts which AFAIK are issues in ABI that can be
improved. I shall post them here as separate emails, four at a time for
clarity.
I need opinions and comments before I make some formal RFCs. Apologies
if these have been discussed at some point of time in the history and
still I have missed them.
--
Supra
reply other threads:[~2016-06-05 7:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9ca4c32a-3c7c-5ec0-1eec-c3770f05c261@gmail.com \
--to=hegdesmailbox@gmail.com \
--cc=gnu-gabi@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).