From: Paul Eggert <eggert@cs.ucla.edu>
To: Andreas Schwab <schwab@suse.de>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org, Bruno Haible <bruno@clisp.org>
Subject: Re: [PATCH v5] posix: Sync tempname with gnulib
Date: Wed, 17 Apr 2024 13:33:30 -0700 [thread overview]
Message-ID: <aec41c2e-3f22-4137-acc6-2c37f0be7d55@cs.ucla.edu> (raw)
In-Reply-To: <mvmwmow5a34.fsf@suse.de>
On 4/17/24 07:37, Andreas Schwab wrote:
> We cannot accept obfuscated code. We have higher standards.
It's purely a matter of style. As someone who actually did the work, I
shouldn't be told that the style I prefer, which is quite clear even if
it's not your style, is "obfuscated" or is not "high standards".
prev parent reply other threads:[~2024-04-17 20:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 12:20 Adhemerval Zanella
2024-04-10 14:30 ` Bruno Haible
2024-04-17 12:26 ` Andreas Schwab
2024-04-17 13:51 ` Bruno Haible
2024-04-17 14:37 ` Andreas Schwab
2024-04-17 17:04 ` Florian Weimer
2024-04-17 20:33 ` Paul Eggert [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=aec41c2e-3f22-4137-acc6-2c37f0be7d55@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=adhemerval.zanella@linaro.org \
--cc=bruno@clisp.org \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.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).