From: Olivier Dion via <help-guix@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: zimoun <zimon.toutoune@gmail.com>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>,
Olivier Dion via <help-guix@gnu.org>
Subject: Re: Questions regarding substitutes with debug output
Date: Fri, 29 Apr 2022 16:53:00 -0400 [thread overview]
Message-ID: <87y1zna9xv.fsf@laura> (raw)
In-Reply-To: <871qxf1wh7.fsf@elephly.net>
On Fri, 29 Apr 2022, Ricardo Wurmus <rekado@elephly.net> wrote:
> Exactly the same way. The first argument to WITH-CHANNELS would be
> (cons C G) and thus P and D would be picked from the set of C and G. C
> and G can be specified with exact commits or branches, just like the
> --channels option to “guix time-machine”.
>
> We already have all the tools for WITH-CHANNELS — that’s (guix
> inferior). We just don’t have a convenient syntax to do this without a
> lot of boilerplate.
Right. It would be great I think. However, time-machine does the job
for now, at least for my case. But it would definitely allow for better
channel granularity. To continue!
--
Olivier Dion
oldiob.dev
next prev parent reply other threads:[~2022-04-29 20:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 17:32 Questions regarding substitutes with debug output Olivier Dion via
2022-04-22 4:22 ` Maxim Cournoyer
2022-04-22 14:29 ` Olivier Dion via
2022-04-24 3:38 ` Maxim Cournoyer
2022-04-24 14:56 ` Olivier Dion via
2022-04-25 4:10 ` Maxim Cournoyer
2022-04-28 8:13 ` zimoun
2022-04-28 8:58 ` Ricardo Wurmus
2022-04-28 14:11 ` Olivier Dion via
2022-04-28 14:18 ` Ricardo Wurmus
2022-04-28 14:25 ` Olivier Dion via
2022-04-29 5:06 ` Ricardo Wurmus
2022-04-28 14:20 ` Olivier Dion via
2022-04-29 8:49 ` zimoun
2022-04-29 14:47 ` Olivier Dion via
2022-04-29 16:01 ` Ricardo Wurmus
2022-04-29 16:17 ` Olivier Dion via
2022-04-29 20:08 ` Ricardo Wurmus
2022-04-29 20:53 ` Olivier Dion via [this message]
2022-05-09 10:33 ` zimoun
2022-05-09 13:33 ` Ricardo Wurmus
2022-05-09 14:37 ` zimoun
2022-04-29 16:06 ` zimoun
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=87y1zna9xv.fsf@laura \
--to=help-guix@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=olivier.dion@polymtl.ca \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@gmail.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).