From: "Zack Weinberg" <zack@owlfolio.org>
To: "Adhemerval Zanella" <adhemerval.zanella@linaro.org>,
"GNU libc development" <libc-alpha@sourceware.org>
Subject: Re: [PATCH 0/4] Remove libcrypt
Date: Wed, 27 Sep 2023 14:25:29 -0400 [thread overview]
Message-ID: <e1cd3b32-eec7-4fe3-8619-77298065ad68@app.fastmail.com> (raw)
In-Reply-To: <72429e6d-5f53-4558-8382-92984a469003@linaro.org>
On Wed, Sep 27, 2023, at 2:19 PM, Adhemerval Zanella Netto wrote:
>> The only piece of my patchset that I think is really worth keeping, is
>> the changes I made to the documentation. How about you go ahead and
>> merge your patchset and then I'll resubmit the doc changes on top of
>> that? Also I'll send a patch moving md5.c to locale/ so we can
>> completely remove the crypt directory (one fewer top-level directory to
>> walk over in the build makes a measurable difference in how long a null
>> incremental build takes).
>
> Joseph asked to remove the shlib-versions entries, so what about I add
> your documentation on top my patch and send a v2?
If you don't mind doing that work, please go ahead.
zw
prev parent reply other threads:[~2023-09-27 18:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 20:48 Zack Weinberg
2023-09-21 20:49 ` [PATCH 1/4] Import Solar Designer's public domain MD5 for use by localedef Zack Weinberg
2023-09-21 20:50 ` [PATCH 2/4] Remove --enable-crypt and --enable-nss-crypt configure options Zack Weinberg
2023-09-21 20:51 ` [PATCH 3/4] Remove documentation of passphrase-hashing functions Zack Weinberg
2023-09-21 20:52 ` [PATCH 4/4] Remove all of the remaining libcrypt code Zack Weinberg
2023-09-27 13:58 ` [PATCH 0/4] Remove libcrypt Adhemerval Zanella Netto
2023-09-27 18:05 ` Zack Weinberg
2023-09-27 18:19 ` Adhemerval Zanella Netto
2023-09-27 18:25 ` Zack Weinberg [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=e1cd3b32-eec7-4fe3-8619-77298065ad68@app.fastmail.com \
--to=zack@owlfolio.org \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
/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.
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).