From: Olivier Dion via <gwl-devel@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org
Subject: Re: Running hello tutorial in container
Date: Fri, 22 Apr 2022 14:42:37 -0400 [thread overview]
Message-ID: <878rrxufhe.fsf@laura> (raw)
In-Reply-To: <87bkwtq8kn.fsf@elephly.net>
On Fri, 22 Apr 2022, Ricardo Wurmus <rekado@elephly.net> wrote:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> I haven’t investigated yet, but I’m pretty sure that’s due to the
>> container wrapper not passing its arguments to the script it wraps.
>> Should be easy to fix.
>
> Fixed in commit 75f0e72ad7171913722a7c9c2905b1fda6cbad7c. Thanks
> again!
Awesome it's working!
--
Olivier Dion
oldiob.dev
prev parent reply other threads:[~2022-04-22 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 21:24 Running hello tutorial in container Olivier Dion via
2022-04-22 18:16 ` Ricardo Wurmus
2022-04-22 18:24 ` Ricardo Wurmus
2022-04-22 18:42 ` Olivier Dion via [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
List information: https://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rrxufhe.fsf@laura \
--to=gwl-devel@gnu.org \
--cc=olivier.dion@polymtl.ca \
--cc=rekado@elephly.net \
/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).