public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: newlib@sourceware.org
Subject: Re: [PATCH 1/5] Simplify rules for creating man pages
Date: Sun, 8 May 2022 15:42:25 -0400	[thread overview]
Message-ID: <YngdIbnc1+jqbQ7L@vapier> (raw)
In-Reply-To: <20220502125518.19808-2-jon.turney@dronecode.org.uk>

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

On 02 May 2022 13:55, Jon Turney wrote:
> Simplify rules for creating docbook XML used to create manpages:
> Updating the output using move-if-change and then unconditionally
> touching the .stamp file doesn't make much sense.

it does make sense.  i explained the point of the stamp file in the
response to your message:
https://sourceware.org/pipermail/newlib/2022/019064.html

tl;dr: it's a common optimization pattern used in the tree.  it avoids
recreating all the docbook & man pages when there is no content change.
-mike

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

  reply	other threads:[~2022-05-08 19:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02 12:55 [PATCH 0/5] Various improvements to newlib manpages build Jon Turney
2022-05-02 12:55 ` [PATCH 1/5] Simplify rules for creating man pages Jon Turney
2022-05-08 19:42   ` Mike Frysinger [this message]
2022-05-02 12:55 ` [PATCH 2/5] Add build avoidance for 'make man' Jon Turney
2022-05-02 12:55 ` [PATCH 3/5] Silence xsltproc when writing manpages Jon Turney
2022-05-02 12:55 ` [PATCH 4/5] Fix warning about duplicate id in docbook XML Jon Turney
2022-05-02 12:55 ` [PATCH 5/5] Generate manpages for functions in chapter sys.tex Jon Turney
2022-05-05  0:37 ` [PATCH 0/5] Various improvements to newlib manpages build Jeff Johnston

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=YngdIbnc1+jqbQ7L@vapier \
    --to=vapier@gentoo.org \
    --cc=jon.turney@dronecode.org.uk \
    --cc=newlib@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).