From: Ruud van der Pas <ruud.vanderpas@oracle.com>
To: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: [gprofng] Numbering convention for documentation?
Date: Mon, 8 Aug 2022 15:04:43 +0000 [thread overview]
Message-ID: <8EECE04B-1A7F-4BE7-8B1B-FC74D5AC5D9C@oracle.com> (raw)
Hi team,
It is high time to update the gprofng user guide and I wonder
whether there is a convention how to number such an update.
We currently have this:
@set EDITION 1.0
@set VERSION 1.0
What should we set for such an update? I plan a substantial
change with a lot more content.
Thanks in advance for the guidance!
Kind regards, Ruud
reply other threads:[~2022-08-08 15:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8EECE04B-1A7F-4BE7-8B1B-FC74D5AC5D9C@oracle.com \
--to=ruud.vanderpas@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).