From: Nick Clifton <nickc@redhat.com>
To: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>,
binutils@sourceware.org
Subject: Re: 2.40 branch now open for updates
Date: Wed, 25 Jan 2023 11:26:27 +0000 [thread overview]
Message-ID: <693f4c04-4ce9-ab53-a4e0-d3ca37781968@redhat.com> (raw)
In-Reply-To: <409c97d1-745a-0cce-1d9d-96d5162015b5@oracle.com>
Hi Vladimir,
> I just committed my fixes for gprofng/29521 [docs] man pages are not in the release tarball
> to the master branch.
> Do you plan to create the 2.40.1 release ?
Not at the moment. Normally I would only make a point release to fix a bug
which seriously breaks the assembler or linker...
Plus - the gprofng documentation is available via the web site, although not
the man page itself, just the pdf and html versions.
> If yes, I would like to make my fixes to the 2.40 branch too.
Please do apply them anyway. That way if there is a point release
it will contain the missing manual pages.
Cheers
Nick
PS. It appears that in order to create the gprofng man page I have
to go into the gprofng/doc directory of my build tree and run "make".
Is this intentional ? (Specifically, is it intentional that running
"make" in the gprofng directory does not build gprofng.1 nor does
running "make all-gprofng" at the top level). Or have I missed
something ? (Possibly I need to reconfigure my build tree ?)
If it is intentional then it may be necessary to update the src-release.sh
script (toplevel of the binutils source directory) so that it includes
the step to build the gprofng.1 file. Otherwise when the next release
is made, the file will not be built and hence not included in the tarball.
prev parent reply other threads:[~2023-01-25 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 15:35 Nick Clifton
2023-01-16 19:11 ` Joseph Myers
2023-01-17 12:04 ` Nick Clifton
2023-01-24 20:47 ` Vladimir Mezentsev
2023-01-25 11:26 ` Nick Clifton [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=693f4c04-4ce9-ab53-a4e0-d3ca37781968@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=vladimir.mezentsev@oracle.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).