From: ng0 <ng0@n0.is>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 30037-done@debbugs.gnu.org
Subject: [bug#30037] [PATCH] gnu: whois: Remove bundled mkpasswd.
Date: Wed, 10 Jan 2018 17:17:46 +0000 [thread overview]
Message-ID: <20180110171746.vdd4yqadg337ytld@abyayala> (raw)
In-Reply-To: <ef6c1808-2f77-ab04-9c8e-bbb234baff72@tobias.gr>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
Tobias Geerinckx-Rice transcribed 2.0K bytes:
> ng0 wrote on 10/01/18 at 15:46:
> > Which is exactly what we concluded in the old thread about this,
> > which I suggested to read. I just should've removed the TODO note a
> > long time ago.
>
> As I wrote in my previous message addressing that exact thread, that
> would have been nice. No harm done beyond some wasted time.
>
> > I still find mkpasswd feels like an historical accident bundling in
> > favor of some OS that relies on it (iirc the old thread or authors
> > replies), but doesn't really matter. Bikeshedding on the highest
> > level of bikesheds I guess.
>
> Yup :-) I've removed the comment in master and am closing the shed.
>
> Kind regards,
>
> T G-R
>
Okay, ty!
--
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
WWW: https://n0.is/a/ :: https://ea.n0.is
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-01-10 16:18 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
2018-01-10 14:46 ` ng0
2018-01-10 15:26 ` bug#30037: " Tobias Geerinckx-Rice
2018-01-10 17:17 ` ng0 [this message]
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=20180110171746.vdd4yqadg337ytld@abyayala \
--to=ng0@n0.is \
--cc=30037-done@debbugs.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.