From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: kamil.konieczny@linux.intel.com
Cc: xorg-announce@lists.x.org, <xorg@lists.x.org>,
<igt-dev@lists.freedesktop.org>
Subject: Re: [ANNOUNCE] igt-gpu-tools 2.4
Date: Tue, 31 Mar 2026 09:52:17 -0700 [thread overview]
Message-ID: <87tstwx7pa.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <82352ddc32109eefa0a06c8df3c8c8e4.kamil.konieczny@linux.intel.com>
On Tue, 31 Mar 2026 04:07:22 -0700, kamil.konieczny@linux.intel.com wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> A new igt-gpu-tools release is available with the following changes:
>
> Release 2.4 (2026-03-31)
> - ------------------------
Not sure, but do these notifications also need to be sent to
dri-devel@lists.freedesktop.org, looks like some people there do something
with this, see here:
https://lore.kernel.org/dri-devel/87v7ecxabq.wl-ashutosh.dixit@intel.com/T/#t
prev parent reply other threads:[~2026-03-31 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 11:07 [ANNOUNCE] igt-gpu-tools 2.4 kamil.konieczny
2026-03-31 16:52 ` Dixit, Ashutosh [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=87tstwx7pa.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=xorg-announce@lists.x.org \
--cc=xorg@lists.x.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