From: Mike Frysinger <vapier@gentoo.org>
To: "R. Diez" <rdiezmail-newlib@yahoo.de>
Cc: newlib@sourceware.org
Subject: Re: [PATCH] libgloss: rename our $subdirs to $SUBDIRS
Date: Wed, 14 Dec 2022 04:17:38 -0500 [thread overview]
Message-ID: <Y5mUsr4zTHv+L9ds@vapier> (raw)
In-Reply-To: <07c45cb1-f61c-69b3-b426-c73ea5677ba9@yahoo.de>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
On 01 Mar 2022 08:33, R. Diez wrote:
>
> > [...]
> > This is harmless, but can be a
> > bit confusing. Rename our $subdirs to $SUBDIRS to avoid this.
>
> The difference between 'subdirs' and 'SUBDIRS' is not great, especially when talking over the phone.
>
> Would it be possible to use LIBGLOSS_SUBDIRS instead?
doesn't seem worth the effort
although this patch is moot once my patches to remove aarch64 & arm configure
scripts is approved as we won't call AC_CONFIG_SUBDIRS anymore which means this
bug won't be triggered.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-12-14 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 7:26 Mike Frysinger
2022-03-01 7:33 ` R. Diez
2022-12-14 9:17 ` Mike Frysinger [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=Y5mUsr4zTHv+L9ds@vapier \
--to=vapier@gentoo.org \
--cc=newlib@sourceware.org \
--cc=rdiezmail-newlib@yahoo.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.
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).