From: Paul Eggert <eggert@cs.ucla.edu>
To: Collin Funk <collin.funk1@gmail.com>, bug-gnulib@gnu.org
Subject: Re: [PATCH 1/4] stdbit: new module
Date: Sun, 12 May 2024 08:23:49 -0700 [thread overview]
Message-ID: <ba073c23-e1fd-491a-aa0b-2bdf54ac34e3@cs.ucla.edu> (raw)
In-Reply-To: <ac4c0e76-8ab3-4a61-b064-dec155451f34@gmail.com>
On 2024-05-11 23:48, Collin Funk wrote:
>> +# stddef_h.m4
>> +# serial 1
> I see that you use my method of making sure files have license
> headers, just copying another file. :)
Thanks, I fixed that.
Is this stuff documented somewhere in the .texi files? If not, I suppose
it should be.
Frankly I continue to be annoyed by having to read and write a line "#
FILENAME.m4" at the start of every m4 file FILENAME.m4. It's better for
a file's first line to be a human-readable comment explaining what the
file is for. Any automated procedure already knows the file name, so why
do we need to put the name there manually, an error-prone process?
next prev parent reply other threads:[~2024-05-12 15:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 19:08 [PATCH 0/4] New stdbit module, for C23 style stdbit.h Paul Eggert
2024-05-11 19:08 ` [PATCH 1/4] stdbit: new module Paul Eggert
2024-05-12 6:48 ` Collin Funk
2024-05-12 15:23 ` Paul Eggert [this message]
2024-05-12 18:43 ` Collin Funk
2024-05-12 19:25 ` Paul Eggert
[not found] ` <4664326.CvnuH1ECHv@nimes>
2024-05-13 21:06 ` Python class comments Collin Funk
2024-05-13 16:57 ` *.m4 conventions Bruno Haible
2024-05-13 19:26 ` Paul Eggert
2024-05-13 20:23 ` Bruno Haible
2024-05-14 2:09 ` Paul Eggert
2024-05-11 19:08 ` [PATCH 2/4] stdbit-tests: new module Paul Eggert
2024-05-13 17:47 ` Bruno Haible
[not found] ` <ddb37f62-e93a-4da2-bdee-94cc4ad1edd4@cs.ucla.edu>
2024-05-13 21:52 ` Bruno Haible
2024-05-11 19:08 ` [PATCH 3/4] stdbit: remove most module dependence Paul Eggert
2024-05-13 21:08 ` Collin Funk
2024-05-11 19:08 ` [PATCH 4/4] stdbit: clean up namespace and simplify Paul Eggert
2024-05-13 16:17 ` considering L1 cache Bruno Haible
2024-05-13 22:44 ` Paul Eggert
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ba073c23-e1fd-491a-aa0b-2bdf54ac34e3@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bug-gnulib@gnu.org \
--cc=collin.funk1@gmail.com \
/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).