all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>, ludo@gnu.org
Cc: 30037@debbugs.gnu.org
Subject: [bug#30037] [PATCH] gnu: whois: Remove bundled mkpasswd.
Date: Tue, 09 Jan 2018 18:05:55 +0100	[thread overview]
Message-ID: <87shbf2c98.fsf@fastmail.com> (raw)
In-Reply-To: <11ef27fb-447c-254e-fd07-6574cdf26ed9@tobias.gr>

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

Tobias Geerinckx-Rice <me@tobias.gr> writes:

> Ludo',
>
> Ludovic Courtès wrote on 09/01/18 at 14:36:
>> LGTM, thanks!
>
> Thanks. However, I'm now convinced that this program is confusingly
> named but belongs where it is, and we should simply remove the TODO
> comment. It's not ‘bundled’ in the sense of the word we use.
>
> If no-one objects I'll do just that & close this bug.

LGTM!

I was just about to write that I actually *use* this software, and
suggest doing the same thing.  It's a convenient tool for generating a
password string suitable for /etc/shadow.  And it's tiny, so separating
it out seems "overkill".

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

  reply	other threads:[~2018-01-09 17:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09  1:01 [bug#30037] [PATCH] gnu: whois: Remove bundled mkpasswd Tobias Geerinckx-Rice
2018-01-09  1:04 ` Tobias Geerinckx-Rice
2018-01-09  6:51 ` ng0
2018-01-09 16:46   ` Tobias Geerinckx-Rice
2018-01-10 14:55     ` ng0
2018-01-10 15:57       ` Tobias Geerinckx-Rice
2018-01-09 13:36 ` Ludovic Courtès
2018-01-09 16:46   ` Tobias Geerinckx-Rice
2018-01-09 17:05     ` Marius Bakke [this message]
2018-01-10 14:46       ` ng0
2018-01-10 15:26         ` bug#30037: " Tobias Geerinckx-Rice
2018-01-10 17:17           ` [bug#30037] " ng0

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=87shbf2c98.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=30037@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=me@tobias.gr \
    /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.