bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: bug-gnulib@gnu.org
Subject: serial number format
Date: Thu, 04 Apr 2024 09:11:05 +0100	[thread overview]
Message-ID: <87o7aph7ja.fsf@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 894 bytes --]

Hi all,

For reasons once might be able to guess, I'm currently playing with
"known" M4 macros vs unseen serials and such.

At the moment, my tool uses the format described at
https://www.gnu.org/software/automake/manual/html_node/Serials.html.

My reading of it implies that the use in e.g. m4/build-to-host.m4
as '# build-to-host.m4 serial 3' isn't valid (I would expect "# serial 3
build-to-host.m4" or similar, closest analogue).

If I grep for serial in gnulib, I see a mix of both the format I
expected and this other format which uses the macro name too.

Are both formats valid (I know it's largely a convention)? Is there a
reason for the apparent inconsistency in format used within e.g. gnulib?
Is there anywhere else I should go read up on conventions for this?

I'll inevitably have to try deal with both formats as they will be in
the wild anyway, but got curious ;)

thanks,
sam

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]

             reply	other threads:[~2024-04-04  8:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04  8:11 Sam James [this message]
2024-04-04 10:45 ` serial number format Bruno Haible
2024-04-04 12:28   ` Sam James
2024-04-04 14:23     ` Bruno Haible
2024-04-07 17:49   ` Paul Eggert
2024-04-07 22:15     ` Bruno Haible
2024-04-07 22:31     ` Sam James

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=87o7aph7ja.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=bug-gnulib@gnu.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).