From: ludo@gnu.org (Ludovic Courtès)
To: Cyril Roelandt <tipecaml@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Add st
Date: Mon, 15 Jun 2015 22:33:06 +0200 [thread overview]
Message-ID: <87h9q867b1.fsf@gnu.org> (raw)
In-Reply-To: <557DBDE1.503@gmail.com> (Cyril Roelandt's message of "Sun, 14 Jun 2015 19:46:09 +0200")
Cyril Roelandt <tipecaml@gmail.com> skribis:
> Not sure whether we want to have suckless.scm. Does it make sense to the
> other devs?
I think people on IRC were OK with the idea.
> If we end up using "suckless.scm", I'd rather rename it first, and then
> add st to it.
Yes, but no big deal.
Ludo’.
next prev parent reply other threads:[~2015-06-15 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 11:04 [PATCH] Add st amirouche
2015-06-09 13:07 ` amirouche
2015-06-09 14:22 ` Andreas Enge
2015-06-10 6:28 ` amirouche
2015-06-11 22:15 ` Mark H Weaver
2015-06-13 19:13 ` amirouche
2015-06-14 17:46 ` Cyril Roelandt
2015-06-15 20:33 ` Ludovic Courtès [this message]
2015-06-15 21:28 ` Mark H Weaver
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=87h9q867b1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=tipecaml@gmail.com \
/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).