From: paren--- via Guix-patches via <guix-patches@gnu.org>
To: 53833@debbugs.gnu.org
Subject: [bug#53833] [PATCH] gnu: Add qbe.
Date: Mon, 25 Apr 2022 20:08:44 +0000 [thread overview]
Message-ID: <b3652409ce29bb4b93043fe7f4b5527239e6dad3@disroot.org> (raw)
In-Reply-To: <20220207011332.27844-1-jgart@dismail.de>
QBE is now being used in one reasonably mature project: https://harelang.org https://harelang.org/
While it's not at 1.0 yet, it's been in development for ~2 (i think) years now.
next prev parent reply other threads:[~2022-04-25 20:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 1:13 [bug#53833] [PATCH] gnu: Add qbe jgart via Guix-patches via
2022-02-07 9:47 ` Liliana Marie Prikler
2022-02-08 21:10 ` jgart via Guix-patches via
2022-04-05 16:11 ` bug#53833: " Ludovic Courtès
2022-04-25 20:08 ` paren--- via Guix-patches via [this message]
2022-04-26 18:16 ` [bug#53833] " paren--- via Guix-patches via
2022-05-07 16:34 ` [bug#53833] QBE and cproc upstreaming paren--- via Guix-patches via
2022-05-07 17:09 ` [bug#53833] [PATCH] gnu: Add qbe (unmatched-parenthesis via Guix-patches via
2022-05-07 17:11 ` [bug#53833] [PATCH] gnu: patches: Add qbe-makefile-add-target.patch (unmatched-parenthesis via Guix-patches via
2022-05-07 17:21 ` [bug#53833] [PATCH] gnu: packages: c: Add (unmatched parenthesis copyright statement (unmatched-parenthesis via Guix-patches via
2022-05-07 18:19 ` [bug#53833] Upstreaming QBE and cproc paren--- via Guix-patches via
2022-05-08 20:21 ` [bug#53833] [PATCH v2] gnu: Add qbe (unmatched-parenthesis via Guix-patches via
2022-05-24 6:50 ` Liliana Marie Prikler
2022-05-24 19:44 ` bug#53833: " Liliana Marie Prikler
[not found] <454d4c514fc4485670cf8f2ec891034c9014edc0@disroot.org>
2022-04-26 7:43 ` [bug#53833] [PATCH] " Liliana Marie Prikler
2022-05-01 13:16 ` Ludovic Courtès
2022-05-02 6:33 ` Liliana Marie Prikler
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=b3652409ce29bb4b93043fe7f4b5527239e6dad3@disroot.org \
--to=guix-patches@gnu.org \
--cc=53833@debbugs.gnu.org \
--cc=paren@disroot.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.