unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, "alírio eyng" <alirioeyng@gmail.com>
Subject: Re: Proposal: Prefix language-name for language library packages
Date: Fri, 06 May 2016 12:20:15 +0200	[thread overview]
Message-ID: <87lh3n7ajk.fsf@gnu.org> (raw)
In-Reply-To: <87poszvfxs.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 06 May 2016 08:49:51 +0200")

Ricardo Wurmus <rekado@elephly.net> skribis:

> alírio eyng <alirioeyng@gmail.com> writes:
>
>> i suggested renaming:
>> readline, libunistring, htslib, c-ares, json-c, icu4c, ...
>> to:
>> c-readline, c-unistring, c-hts, c-ares, c-json, c-icu, ...
>>
>> no replies, is that implicit agreement?
>
> I strongly disagree with this as it makes things needlessly confusing,
> in my opinion.

+1

We joked about adding this “c-” prefix earlier in this discussion, but
that’s really just a joke.

Thanks,
Ludo’.

  reply	other threads:[~2016-05-06 10:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28  8:45 Proposal: Prefix language-name for language library packages alírio eyng
2016-04-29 18:31 ` alírio eyng
2016-04-29 23:36   ` Leo Famulari
2016-04-30  6:38     ` Ricardo Wurmus
2016-05-02  7:50       ` Ludovic Courtès
2016-05-02  9:33         ` ng0
2016-05-02 18:33         ` Leo Famulari
2016-05-06  2:45           ` alírio eyng
2016-05-06  6:49             ` Ricardo Wurmus
2016-05-06 10:20               ` Ludovic Courtès [this message]
2016-05-06 20:12             ` Andreas Enge
2016-05-07  0:32               ` John Darrington
2016-05-01  3:00     ` alírio eyng
  -- strict thread matches above, loose matches on Subject: below --
2016-04-24 13:22 Hartmut Goebel
2016-04-24 16:00 ` Danny Milosavljevic
2016-04-24 18:57 ` Leo Famulari
2016-04-24 22:13   ` Hartmut Goebel
2016-04-28 11:48   ` Ludovic Courtès
2016-04-28 11:56 ` Ludovic Courtès
2016-04-28 16:04   ` Leo Famulari

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=87lh3n7ajk.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alirioeyng@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 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).