From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Gentoo derived distributions? -> Gentoo Ecosystem timeline
Date: Tue, 31 Jan 2017 20:59:43 +0100 [thread overview]
Message-ID: <2297805.IFt7AJW3bC@pinacolada> (raw)
In-Reply-To: <60c73bfc-e392-0ca0-9ff7-5a02e5a84cfb@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
>
> Name: Adélie Linux
> Founded: 2015-10-02
> Derived-from: Gentoo
> Homepage: https://adelielinux.org
This one I've already added (though the earliest blog post I found was from
2016-08).
>
> Name: Galapagos Linux
> Founded: 2016-11-03
> Derived-from: Gentoo
> Homepage: https://glpgs.io
That's a bit too alpha right now imho... :) the resulting dot will barely fit
between Novemeber and now...
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2017-01-31 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 19:05 [gentoo-project] Gentoo derived distributions? -> Gentoo Ecosystem timeline Andreas K. Huettel
2017-01-31 19:48 ` Daniel Campbell
2017-01-31 19:59 ` Andreas K. Huettel [this message]
2017-02-01 7:10 ` Ulrich Mueller
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2297805.IFt7AJW3bC@pinacolada \
--to=dilfridge@gentoo.org \
--cc=gentoo-project@lists.gentoo.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