From: Attila Lendvai <attila@lendvai.name>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Mechanism for helping in multi-channels configuration
Date: Tue, 12 Mar 2024 12:44:51 +0000 [thread overview]
Message-ID: <sYjSC7sIywtFyzIAQT6kMijHmnbcpb3Q3BjMdigqjbtESSO51wvki4p6BH66X1izPCl-qK7WKUMzr8Qej85nGdeIx6PcY29Kp1Gm6946ZEc=@lendvai.name> (raw)
In-Reply-To: <8734tt5t1y.fsf@gmail.com>
> Although I concur with this need, I do not see how it would be help for
> detecting compatibility between channels. :-)
maybe i'm overthinking this, and all we need is a way to point to git commit ranges that are compatible.
more specifically, i'm maintaining the guix-crypto channel, and i often miss the ability to point to a guix commit, beyond which there is a change in guix that my channel is not yet compatible with. if my users issue a `guix pull`, then it would not pull the guix channel beyond that commit, and warn the users that it's being held back.
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“In the electronics industry, patents are of no value whatsoever in spurring research and development.”
— vice-president of Intel Corporation, Business Week, 11 May 1981.
prev parent reply other threads:[~2024-03-12 12:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 10:36 Mechanism for helping in multi-channels configuration Simon Tournier
2024-02-03 15:27 ` Christina O'Donnell
2024-02-15 15:05 ` Simon Tournier
2024-03-18 16:05 ` Mechanism for helping in multi-channels configuration (and Xapian index) Christina O'Donnell
2024-05-06 12:05 ` Simon Tournier
2024-02-06 14:18 ` Mechanism for helping in multi-channels configuration Maxim Cournoyer
2024-02-06 17:08 ` Attila Lendvai
2024-02-06 17:16 ` Attila Lendvai
2024-02-15 21:14 ` Simon Tournier
2024-03-12 12:44 ` Attila Lendvai [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='sYjSC7sIywtFyzIAQT6kMijHmnbcpb3Q3BjMdigqjbtESSO51wvki4p6BH66X1izPCl-qK7WKUMzr8Qej85nGdeIx6PcY29Kp1Gm6946ZEc=@lendvai.name' \
--to=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).