all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: guix-devel@gnu.org
Cc: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Subject: Re: Python package naming: Dots vs hyphens
Date: Wed, 06 Nov 2019 14:53:04 +0100	[thread overview]
Message-ID: <87eeylun5r.fsf@nckx> (raw)
In-Reply-To: <20191106071917.GJ14453@E5400>

[-- Attachment #1: Type: text/plain, Size: 352 bytes --]

Florian,

Efraim Flashner 写道：
> For new packages I would use whatever upstream uses in regard to 
> '-' vs
> '.'. For existing ones, how many are there? It might be best to 
> just
> leave them as-is rather than go through the dance of deprecating 
> the old
> packages.

I agree with Efraim on both points.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2019-11-06 13:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06  6:49 Python package naming: Dots vs hyphens pelzflorian (Florian Pelz)
2019-11-06  7:19 ` Efraim Flashner
2019-11-06 13:13   ` pelzflorian (Florian Pelz)
2019-11-07  7:34     ` Efraim Flashner
2019-11-06 13:18   ` Mailman packaging (was: Re: Python package naming: Dots vs hyphens) pelzflorian (Florian Pelz)
2019-11-13 22:16     ` pelzflorian (Florian Pelz)
2019-11-18 10:13     ` Efraim Flashner
2019-11-18 13:14       ` pelzflorian (Florian Pelz)
2019-11-20 16:36       ` Pjotr Prins
2021-09-29 16:34       ` Christine Lemmer-Webber
2021-09-30  7:54         ` pelzflorian (Florian Pelz)
2019-11-06 13:53   ` Tobias Geerinckx-Rice [this message]
2019-11-10 10:57 ` Python package naming: Dots vs hyphens Andreas Enge
2019-11-11  9:30   ` Efraim Flashner
2019-11-11 10:24     ` pelzflorian (Florian Pelz)

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=87eeylun5r.fsf@nckx \
    --to=me@tobias.gr \
    --cc=guix-devel@gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    /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.