From: jgart <jgart@dismail.de>
To: Julien Lepiller <julien@lepiller.eu>
Cc: help-guix@gnu.org
Subject: Re: committer.scm
Date: Tue, 1 Nov 2022 17:19:32 -0500 [thread overview]
Message-ID: <20221101171932.GB13253@dismail.de> (raw)
In-Reply-To: <FC48DF54-1060-416B-9106-3A50F3EE42CE@lepiller.eu>
On Tue, 01 Nov 2022 07:57:28 +0100 Julien Lepiller <julien@lepiller.eu> wrote:
> Try calling it with pre-inst-env.
Ohhh, yes that was it. I stopped calling it with pre-inst-env for some reason ;()
THNX
Now I just need to see how I am going to sort these 150+ crates in an automated fashion...
next prev parent reply other threads:[~2022-11-01 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 1:42 committer.scm jgart
2022-11-01 6:57 ` committer.scm Julien Lepiller
2022-11-01 22:19 ` jgart [this message]
2022-11-02 9:19 ` committer.scm Csepp
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221101171932.GB13253@dismail.de \
--to=jgart@dismail.de \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
/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).