From: Bikutoso <Bikutoso@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] bacon: update to 4.4.
Date: Wed, 10 Nov 2021 21:35:04 +0100 [thread overview]
Message-ID: <20211110203504.dIGg21TMhUn4srIpPK9T-88hOhfI37A5PyZdX5AlKyk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33977@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
New review comment by Bikutoso on void-packages repository
https://github.com/void-linux/void-packages/pull/33977#discussion_r746965547
Comment:
> If you can tell me some simple steps to use it, I can test locally on musl.
What I meant is that I'm worried that it might fail to build after being merged. As I tried to build it in a VM and it ended up with a segfault.
Using it is simple enough. Just run `bacon` (or `bacon.sh`?) with the file to make. e.g. `bacon hello.bac`
Their website has a bunch of [example](http://basic-converter.org/#examples) code.
next prev parent reply other threads:[~2021-11-10 20:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 13:00 [PR PATCH] " Bikutoso
2021-11-09 13:51 ` [PR PATCH] [Closed]: " Bikutoso
2021-11-09 14:40 ` ericonr
2021-11-09 15:18 ` Bikutoso
2021-11-09 19:31 ` ericonr
2021-11-09 21:54 ` [PR PATCH] [Updated] " Bikutoso
2021-11-09 22:25 ` Bikutoso
2021-11-10 0:25 ` ericonr
2021-11-10 0:46 ` [PR REVIEW] " ericonr
2021-11-10 13:27 ` [PR PATCH] [Updated] " Bikutoso
2021-11-10 13:47 ` [PR REVIEW] " Bikutoso
2021-11-10 13:49 ` Bikutoso
2021-11-10 18:54 ` ericonr
2021-11-10 20:35 ` Bikutoso [this message]
2021-11-10 20:35 ` Bikutoso
2021-11-10 22:29 ` ericonr
2021-11-10 22:40 ` ericonr
2021-11-10 22:40 ` ericonr
2021-11-10 23:07 ` [PR PATCH] [Updated] " Bikutoso
2021-11-11 0:22 ` [PR PATCH] [Merged]: " ericonr
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=20211110203504.dIGg21TMhUn4srIpPK9T-88hOhfI37A5PyZdX5AlKyk@z \
--to=bikutoso@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).