From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Ricardo Wurmus <rekado@elephly.net>, 28487@debbugs.gnu.org
Subject: [bug#28487] [PATCH] cuirass: Add gnu-system build spec.
Date: Thu, 28 Sep 2017 18:04:24 +0200 [thread overview]
Message-ID: <87shf6q06v.fsf@gnu.org> (raw)
In-Reply-To: <87r2urz0q9.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 28 Sep 2017 10:27:58 +0200")
Ludovic Courtès writes:
>> (match o
>> (($ <license>) ...)
>
> I would make it:
>
> (match o
> ((? license?)
> ...))
Oops, something like this was already pushed here:
> Anyway, with this fixed, OK to push.
Thanks, pushed with all this fixed to master as 516b53828e90018126b79e7600cae9aa531e06d7
Sure hope I didn't interpret the OK to push too lightly. Mentioned
commit above is the second patch, the first is here
http://git.savannah.gnu.org/cgit/guix.git/commit/?id=66bc1d2aaf74fc7eb4ef9b3519c69bd37142ffb3
>> so I was wondering why you didn't export <license>. Now it makes sense:
>> you simply cannot use record destructors if you don't export <..> in the
>> first place. For GOOPS that's a bit different, you don't have class?
>> for each <class>.
>
> Yes. I think the “spirit of GOOPS” is that class objects are public.
Yeah...and then you have to be `careful'; not so nice come to think of it.
Greetings,
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2017-09-28 16:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 20:11 [bug#28484] Some steps and questions for Cuirass Jan Nieuwenhuizen
2017-09-17 20:11 ` [bug#28485] [PATCH 1/3] base: Make working copy writable Jan Nieuwenhuizen
[not found] ` <handler.28485.B.1505679193775.ack@debbugs.gnu.org>
2017-09-18 15:46 ` bug#28485: Acknowledgement ([PATCH 1/3] base: Make working copy writable.) Jan Nieuwenhuizen
2017-09-17 20:11 ` [bug#28486] [PATCH 2/3] gnu-system: Accept subset with list of package names Jan Nieuwenhuizen
[not found] ` <handler.28486.B.1505679194784.ack@debbugs.gnu.org>
2017-09-18 15:45 ` bug#28486: Acknowledgement ([PATCH 2/3] gnu-system: Accept subset with list of package names.) Jan Nieuwenhuizen
2017-09-17 20:11 ` [bug#28488] [PATCH 3/3] base: Show feedback when build has finished Jan Nieuwenhuizen
[not found] ` <handler.28488.B.1505679198802.ack@debbugs.gnu.org>
2017-09-18 15:48 ` bug#28488: Acknowledgement ([PATCH 3/3] base: Show feedback when build has finished.) Jan Nieuwenhuizen
2017-09-17 20:11 ` [bug#28487] [PATCH] cuirass: Add gnu-system build spec Jan Nieuwenhuizen
2017-09-26 8:18 ` Ludovic Courtès
2017-09-26 17:56 ` Jan Nieuwenhuizen
2017-09-26 18:05 ` Jan Nieuwenhuizen
2017-09-26 20:29 ` Ludovic Courtès
2017-09-27 18:55 ` Jan Nieuwenhuizen
2017-09-27 19:45 ` Ludovic Courtès
2017-09-27 20:32 ` Jan Nieuwenhuizen
2017-09-27 20:52 ` Jan Nieuwenhuizen
2017-09-28 8:26 ` Ludovic Courtès
2017-09-28 15:41 ` bug#28487: " Jan Nieuwenhuizen
2017-09-28 8:27 ` [bug#28487] " Ludovic Courtès
2017-09-28 16:04 ` Jan Nieuwenhuizen [this message]
2017-09-18 11:51 ` [bug#28484] Some steps and questions for Cuirass Mathieu Othacehe
2017-09-18 15:44 ` bug#28484: " Jan Nieuwenhuizen
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=87shf6q06v.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=28487@debbugs.gnu.org \
--cc=ludo@gnu.org \
--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.
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).