From: Vincent Legoll <vincent.legoll@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Document our WIP
Date: Sat, 27 Mar 2021 16:50:17 +0100 [thread overview]
Message-ID: <CAEwRq=q_8dGPydnLAYw7DRA4J2r5AMtJqLpFyMtvgMRtqdFcBQ@mail.gmail.com> (raw)
In-Reply-To: <CAEwRq=oyccxtUsZa_Z6HUTaTkkkb0nskUuAE1UDOxu0aP9_BfQ@mail.gmail.com>
Looks like we have a plan.
Now for the hard part, how do we name it ?
"Guix/WIP" or "Guix/WorkInProgress"
or
"Guix/Hacking", "Guix/CoolStuff", "Guix/BleedingEdge", "Guix/NewShiny"
Some of those may be half-jokes, I'd personally go with WorkInProgress.
--
Vincent Legoll
next prev parent reply other threads:[~2021-03-27 15:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 10:07 Document our WIP Vincent Legoll
2021-03-27 14:20 ` Léo Le Bouter
2021-03-27 14:44 ` Ricardo Wurmus
2021-03-27 15:32 ` Joshua Branson
2021-03-27 15:34 ` Léo Le Bouter
2021-03-27 15:44 ` Luis Felipe
2021-03-27 15:54 ` Léo Le Bouter
2021-03-27 15:41 ` Vincent Legoll
2021-03-27 15:50 ` Vincent Legoll [this message]
2021-03-27 15:54 ` Luis Felipe
2021-03-27 16:03 ` Vincent Legoll
2021-03-27 16:04 ` Léo Le Bouter
2021-03-27 16:42 ` Luis Felipe
2021-03-27 16:50 ` Léo Le Bouter
2021-03-27 17:02 ` Luis Felipe
2021-03-27 17:05 ` Vincent Legoll
2021-03-27 18:12 ` Vincent Legoll
2021-03-27 18:18 ` Luis Felipe
2021-03-28 15:33 ` Vincent Legoll
2021-03-27 17:02 ` Vincent Legoll
2021-03-27 18:11 ` Luis Felipe
2021-03-27 18:13 ` Vincent Legoll
2021-03-27 16:01 ` Léo Le Bouter
2021-03-30 10:37 ` Ludovic Courtès
2021-03-31 17:52 ` Léo Le Bouter
2021-03-31 18:16 ` Leo Famulari
2021-04-01 21:33 ` Luis Felipe
2021-04-02 16:11 ` Léo Le Bouter
2021-04-08 19:55 ` Luis Felipe
2021-04-08 21:06 ` Vincent Legoll
2021-04-02 4:42 ` Gurjeet Singh
2021-04-05 23:35 ` Léo Le Bouter
2021-04-07 15:55 ` Vincent Legoll
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='CAEwRq=q_8dGPydnLAYw7DRA4J2r5AMtJqLpFyMtvgMRtqdFcBQ@mail.gmail.com' \
--to=vincent.legoll@gmail.com \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.