From: Ruud van der Pas <ruud.vanderpas@oracle.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Jan Beulich via Binutils <binutils@sourceware.org>,
Jose Marchesi <jose.marchesi@oracle.com>
Subject: Re: gprofng not quite ready for prime time?
Date: Thu, 11 Aug 2022 15:41:51 +0000 [thread overview]
Message-ID: <79B87456-37F9-49D6-900F-35A1670C7F09@oracle.com> (raw)
In-Reply-To: <08adcc0b-2ca1-61ee-75be-c11e2c5f49ab@suse.com>
Hi Jan,
> Take the time stamp of the newest file in the doc dir (or a subset thereof)?
> With how git works, this may of course still not be what you want, so the
> next approach then would be to actually query git (as long as you're in a
> git tree) for the newest commit's date touching any of the relevant files.
> Sounds all quite a bit more involved than simply using the time when the
> build was done.
Thanks for the suggestions.
It is indeed somewhat tricky. Let me check what others do regarding
the docs in binutils. If there is sufficient commonality in their approach,
I can just do the same, or at least do something similar.
Kind regards, Ruud
prev parent reply other threads:[~2022-08-11 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 13:57 Jan Beulich
2022-08-09 14:33 ` Luis Machado
2022-08-09 18:17 ` Ruud van der Pas
2022-08-10 6:58 ` Jan Beulich
2022-08-10 11:06 ` Jose E. Marchesi
2022-08-11 11:43 ` Ruud van der Pas
2022-08-11 12:23 ` Jan Beulich
2022-08-11 14:02 ` Ruud van der Pas
2022-08-11 14:23 ` Jan Beulich
2022-08-11 15:41 ` Ruud van der Pas [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=79B87456-37F9-49D6-900F-35A1670C7F09@oracle.com \
--to=ruud.vanderpas@oracle.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=jose.marchesi@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).