From: Nick Clifton <nickc@redhat.com>
To: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: Patch for version.texi?
Date: Tue, 18 Jul 2023 16:29:45 +0100 [thread overview]
Message-ID: <db3303a2-4c42-7d1d-0718-a8498864b8d7@redhat.com> (raw)
In-Reply-To: <62b68369-0d02-3472-bbe6-cb627661252e@oracle.com>
Hi Vladimir,
> -@set UPDATED 14 April 2022
> -@set UPDATED-MONTH April 2022
> +@set UPDATED 17 April 2023
> +@set UPDATED-MONTH April 2023
> My questions:
> Should I update gprofng/doc/version.texi now ?
Well my sources show that it has already been updated to 18 April 2023,
so I guess that this question is moot.
> Should I update gprofng/doc/version.texi in [2.41] or the file will be updated automatically.
It will be updated automatically.
One of the steps involved in creating the 2.41 release is to rebuild
all of the sources with maintainer mode enabled.
Cheers
Nick
prev parent reply other threads:[~2023-07-18 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bee3c955-ed3a-3106-040c-6f0146edb2bf@oracle.com>
2023-07-13 2:35 ` Vladimir Mezentsev
2023-07-18 15:29 ` 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=db3303a2-4c42-7d1d-0718-a8498864b8d7@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).