From: jgart via Guix-patches via <guix-patches@gnu.org>
To: bil@ccrma.Stanford.EDU
Cc: Guillaume Le Vaillant <glv@posteo.net>,
Pierre Neidhardt <mail@ambrevar.xyz>,
51903@debbugs.gnu.org
Subject: [bug#51903] cmn license etc
Date: Sun, 21 Nov 2021 19:30:45 -0500 [thread overview]
Message-ID: <20211121193045.GB7334@gac.attlocal.net> (raw)
In-Reply-To: <6d040ba1b363019b7d0e6b36b2a9af38@ccrma.stanford.edu>
On Sun, 21 Nov 2021 11:22:21 -0800 bil@ccrma.Stanford.EDU wrote:
> Oh hell. I'm forgetting CL. My apologies. Your fix
> was probably correct.
>
Hi everyone,
It's great that this was able to be resolved.
I'm looking forward to having a cmn package for guix.
Guillaume would you be so kind to send your patch to Bill?
Bill, would that be helpful?
I can then update the guix package to use the newer version of cmn once it is released and avoid
having to patch the asd file.
all the best,
jgart
next prev parent reply other threads:[~2021-11-22 0:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 1:52 [bug#51903] [PATCH] gnu: Add cl-cmn jgart via Guix-patches via
2021-11-17 7:49 ` Pierre Neidhardt
2021-11-17 8:50 ` jgart via Guix-patches via
2021-11-17 9:24 ` Pierre Neidhardt
2021-11-17 8:55 ` [bug#51903] [PATCH v2] " jgart via Guix-patches via
2021-11-17 10:39 ` [bug#51903] cmn license etc bil
2021-11-21 12:51 ` Guillaume Le Vaillant
2021-11-21 14:16 ` bil
2021-11-21 16:20 ` Guillaume Le Vaillant
2021-11-21 17:45 ` bil
2021-11-21 17:54 ` Guillaume Le Vaillant
2021-11-21 19:22 ` bil
2021-11-22 0:30 ` jgart via Guix-patches via [this message]
2021-11-22 10:10 ` Guillaume Le Vaillant
2021-11-22 14:13 ` bil
2021-11-22 18:35 ` [bug#51903] [PATCH v3] gnu: Add cl-cmn jgart via Guix-patches via
2021-11-22 19:45 ` bug#51903: " Guillaume Le Vaillant
2021-11-22 20:11 ` [bug#51903] " jgart via Guix-patches via
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=20211121193045.GB7334@gac.attlocal.net \
--to=guix-patches@gnu.org \
--cc=51903@debbugs.gnu.org \
--cc=bil@ccrma.Stanford.EDU \
--cc=glv@posteo.net \
--cc=jgart@dismail.de \
--cc=mail@ambrevar.xyz \
/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).