qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH] tracetool: use relative paths for '#line' preprocessor directives
Date: Sun, 9 Apr 2023 08:50:29 -0400	[thread overview]
Message-ID: <CAJSP0QUZT=6ZGTqXkSwJvsCfPG0-A00f174N=NJcp__XtANNAA@mail.gmail.com> (raw)
In-Reply-To: <20230406080045.21696-1-thomas.de_schampheleire@nokia.com>

On Thu, 6 Apr 2023 at 09:22, Thomas De Schampheleire
<thomas.de_schampheleire@nokia.com> wrote:
>
> The event filename is an absolute path. Convert it to a relative path when
> writing '#line' directives, to preserve reproducibility of the generated
> output when different base paths are used.
>
> Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
> ---
>  scripts/tracetool/backend/ftrace.py | 4 +++-
>  scripts/tracetool/backend/log.py    | 4 +++-
>  scripts/tracetool/backend/syslog.py | 4 +++-
>  3 files changed, 9 insertions(+), 3 deletions(-)

Thanks, applied to my block-next tree:
https://gitlab.com/stefanha/qemu/-/tree/block-next

qemu.git/master is currently frozen for the 8.0 release. The latest
release candidate is -rc3 and the final release is imminent. I don't
want to risk breaking and delaying the release at this stage, so I
have queued up this patch for the 8.1 release cycle.

The timing is unlucky, I would have liked to still include this in the
8.0 release. Thank you for the patch!

Stefan


  reply	other threads:[~2023-04-09 12:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06  8:00 [PATCH] tracetool: use relative paths for '#line' preprocessor directives Thomas De Schampheleire
2023-04-09 12:50 ` Stefan Hajnoczi [this message]
2023-04-11 10:44 ` Philippe Mathieu-Daudé

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='CAJSP0QUZT=6ZGTqXkSwJvsCfPG0-A00f174N=NJcp__XtANNAA@mail.gmail.com' \
    --to=stefanha@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thomas.de_schampheleire@nokia.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 NNTP newsgroup(s).