From: Mark Wielaard <mark@klomp.org>
To: Vivek Das Mohapatra <vivek@collabora.com>
Cc: Florian Weimer <fweimer@redhat.com>,
GNU gABI gnu-gabi <gnu-gabi@sourceware.org>
Subject: Re: ABI document
Date: Fri, 14 Aug 2020 17:17:50 +0200 [thread overview]
Message-ID: <e0160519c7b27ae131675a1307acfe722eac2a29.camel@klomp.org> (raw)
In-Reply-To: <alpine.DEB.2.20.2008141232410.15075@noise.cbg.collabora.co.uk>
Hi,
On Fri, 2020-08-14 at 12:33 +0100, Vivek Das Mohapatra via Gnu-gabi
wrote:
> > The GNU Gabi now has a git backed website to document these things
> >
> > https://sourceware.org/gnu-gabi
>
> Nice: Any particular preferred format?
Lets stick to plain text for now. Just so we have something that can
simply be converted into anything. Best to start with content before
worrying about format IMHO.
There are some other gABI extensions that use LaTeX, so we could adopt
that to reuse some structure. But personally I would prefer some
simpler markup language like StructuredText (rst) or MarkDown (md). I
believe Cary was converting the actual gABI spec into MarkDown.
Cheers,
Mark
next prev parent reply other threads:[~2020-08-14 15:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 11:47 Florian Weimer
2020-07-29 11:53 ` Mark Wielaard
2020-07-29 12:15 ` H.J. Lu
2020-07-29 12:22 ` Florian Weimer
2020-08-14 9:51 ` Vivek Das Mohapatra
2020-08-14 10:58 ` Mark Wielaard
2020-08-14 11:33 ` Vivek Das Mohapatra
2020-08-14 15:17 ` Mark Wielaard [this message]
2020-08-27 16:52 ` Vivek Das Mohapatra
2020-08-31 12:54 ` Florian Weimer
2020-09-02 17:29 ` Vivek Das Mohapatra
2020-09-08 12:09 ` Vivek Das Mohapatra
2020-09-16 13:57 ` Vivek Das Mohapatra
2020-09-21 13:03 ` Florian Weimer
2020-09-21 12:36 ` Florian Weimer
2020-11-27 15:40 ` Vivek Das Mohapatra
2020-11-30 17:36 ` Florian Weimer
2020-12-09 16:59 ` Vivek Das Mohapatra
2022-08-25 8:11 ` Florian Weimer
2022-08-25 15:38 ` Carlos O'Donell
2022-08-30 11:55 ` Vivek Dasmohapatra
2022-08-30 12:12 ` Florian Weimer
2022-08-30 15:17 ` Vivek Dasmohapatra
2020-07-29 12:56 ` Jose E. Marchesi
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=e0160519c7b27ae131675a1307acfe722eac2a29.camel@klomp.org \
--to=mark@klomp.org \
--cc=fweimer@redhat.com \
--cc=gnu-gabi@sourceware.org \
--cc=vivek@collabora.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).