From: "BlueT - Matthew Lien - 練喆明" <bluet@bluet.org>
To: Amirouche Boubekki <amirouche.boubekki@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>,
gnu-system-discuss@gnu.org, Guile User <guile-user@gnu.org>,
help-guix@gnu.org, guile-sources@gnu.org
Subject: Re: GNU Guix 1.0.0 released
Date: Sat, 4 May 2019 08:56:50 +0800 [thread overview]
Message-ID: <CAGurB_hoEDk8XQpTKZvdHpyLkGbzEahOPRJo-1=qN=nSZA2==Q@mail.gmail.com> (raw)
In-Reply-To: <CAL7_Mo9NJOj=kBdwW4R4ZmBgWyGT24pOdgN9hj9qZt+54Ubscg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
Years passed, so glad I can see it really coming finally.
Congrats and Thank you all Guix Gurus!
- BlueT
On Sat, May 4, 2019 at 8:28 AM Amirouche Boubekki <
amirouche.boubekki@gmail.com> wrote:
>
>
> Le jeu. 2 mai 2019 à 14:12, Ludovic Courtès <ludo@gnu.org> a écrit :
>
>> We are thrilled to announce the release of GNU Guix 1.0.0!
>>
>> This 1.0 release is a major milestone for Guix. It represents 7 years
>> of hard work with more than 40,000 commits by 260 people, 19 releases,
>> and an equally amazing amount of work on documentation, translation,
>> artwork, web design, mentoring, outreach, and many other activities that
>> together have made it a thriving project.
>>
>
> I would like to add that the maitainers in many places had the vision. The
> first
> being getting started with guix. The dedication is inspiration. Sadly I
> did help
> as much as I could. I had bad experience with packaging stuff. I know it
> is
> easier with guix but still. I also know that not everything in guile is
> about
> packaging. I am happy my graph hack was reworked to be part of guile
> proper.
>
>
> Anyway Happy 1.0.0
>
--
/ Just another [ Perl | FLOSS | Security ] Hacker. /
/ BlueT = Matthew Lien = 練喆明 /
/ http://BlueT.org /
/ GPG: 4A293CBD /
[-- Attachment #2: Type: text/html, Size: 2470 bytes --]
next prev parent reply other threads:[~2019-05-04 0:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 12:12 GNU Guix 1.0.0 released Ludovic Courtès
2019-05-02 12:45 ` Arne Babenhauserheide
2019-05-02 13:03 ` pelzflorian (Florian Pelz)
2019-05-02 13:11 ` pelzflorian (Florian Pelz)
2019-05-02 16:25 ` Thompson, David
2019-05-02 21:27 ` Christopher Lemmer Webber
2019-05-03 7:08 ` Jérémy Korwin-Zmijowski
2019-05-03 14:43 ` Katherine Cox-Buday
2019-05-04 0:18 ` David Pirotte
2019-05-03 20:09 ` Nala Ginrut
2019-05-03 23:26 ` vikram sai balaji ulaganathan
2019-05-03 23:12 ` Matt Wette
2019-05-04 0:27 ` Amirouche Boubekki
2019-05-04 0:56 ` BlueT - Matthew Lien - 練喆明 [this message]
2019-05-04 2:35 ` Jude Rubini
2019-05-04 15:43 ` Dimakakos Dimos
2019-05-04 16:19 ` Sharad Pratap
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGurB_hoEDk8XQpTKZvdHpyLkGbzEahOPRJo-1=qN=nSZA2==Q@mail.gmail.com' \
--to=bluet@bluet.org \
--cc=amirouche.boubekki@gmail.com \
--cc=gnu-system-discuss@gnu.org \
--cc=guile-sources@gnu.org \
--cc=guile-user@gnu.org \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
/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).