From: Nick Alcock <nick.alcock@oracle.com>
To: binutils@sourceware.org
Subject: Re: [PATCH] libctf: merge doc subdir up a level
Date: Wed, 01 Dec 2021 16:53:58 +0000 [thread overview]
Message-ID: <87r1awz2op.fsf@esperi.org.uk> (raw)
In-Reply-To: <542d1970-52c0-4e5d-0e1c-6c6d8c1403f7@redhat.com> (Nick Clifton via Binutils's message of "Wed, 1 Dec 2021 15:16:56 +0000")
On 1 Dec 2021, Nick Clifton via Binutils said:
> Hi Mike,
>
>> This avoids a recursive make into the doc subdir and speeds up the
>> build slightly. It also allows for more parallelism.
>
> Will this have the same problems as the change for the bfd directory's documentation ?
I just copied the bfd directory's documentation framework, so I would
expect at least some problems to be shared with it. (However, we're not
using chew here -- at least, not yet -- so chew-associated problems
would not be expected.)
>> libctf/Makefile.am | 15 +-
>> libctf/Makefile.in | 583 ++++++++++++-------
>> libctf/configure.ac | 2 +-
>> libctf/doc/Makefile.in | 808 ---------------------------
>> libctf/doc/{Makefile.am => local.mk} | 16 +-
>> 5 files changed, 410 insertions(+), 1014 deletions(-)
>> delete mode 100644 libctf/doc/Makefile.in
>> rename libctf/doc/{Makefile.am => local.mk} (71%)
>
> If not then approved - please apply.
Looks good to me too -- less build-system noise and faster, good all
round (assuming it works :) ).
next prev parent reply other threads:[~2021-12-01 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 1:45 Mike Frysinger
2021-12-01 15:16 ` Nick Clifton
2021-12-01 16:53 ` Nick Alcock [this message]
2021-12-02 4:41 ` Mike Frysinger
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=87r1awz2op.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=binutils@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).