public inbox for dtrace@lists.linux.dev
 help / color / mirror / Atom feed
From: eugene.loh@oracle.com
To: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: [PATCH 3/3] NEWS/dtrace.spec: 2.0.5-2 release
Date: Tue, 10 Feb 2026 15:16:37 -0500	[thread overview]
Message-ID: <20260210201637.8863-3-eugene.loh@oracle.com> (raw)
In-Reply-To: <20260210201637.8863-1-eugene.loh@oracle.com>

From: Eugene Loh <eugene.loh@oracle.com>

Update version to 2.0.5-2 in a few overlooked places.

Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
---
 NEWS        | 2 +-
 dtrace.spec | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/NEWS b/NEWS
index 9c62e523b..c76ac114f 100644
--- a/NEWS
+++ b/NEWS
@@ -1,4 +1,4 @@
-2.0.5-1 (Feb 4th, 2026)
+2.0.5-2 (Feb 4th, 2026)
 ------------------------
 
 New features:
diff --git a/dtrace.spec b/dtrace.spec
index d6af5a80e..54d8f1239 100644
--- a/dtrace.spec
+++ b/dtrace.spec
@@ -230,7 +230,7 @@ systemctl start dtprobed || :
 %{_libdir}/dtrace/testsuite
 
 %changelog
-* Wed Feb  4 2026 Eugene Loh <eugene.loh@oracle.com> - 2.0.5-1
+* Wed Feb  4 2026 Eugene Loh <eugene.loh@oracle.com> - 2.0.5-2
 - Implement PID-specific uprobes.  (Kris Van Hees)
 - Allocate the buffers BPF map to fit highest CPU id.  (Kris Van Hees)
 - Fix argument handling for multi-location user probes.
-- 
2.47.3


  parent reply	other threads:[~2026-02-10 20:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 20:16 [PATCH 1/3] Fix init_disassemble_info typo eugene.loh
2026-02-10 20:16 ` [PATCH 2/3] NEWS: Fix indentation eugene.loh
2026-02-10 20:45   ` Kris Van Hees
2026-02-10 20:16 ` eugene.loh [this message]
2026-02-10 20:45   ` [PATCH 3/3] NEWS/dtrace.spec: 2.0.5-2 release Kris Van Hees
2026-02-10 20:45 ` [PATCH 1/3] Fix init_disassemble_info typo Kris Van Hees

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=20260210201637.8863-3-eugene.loh@oracle.com \
    --to=eugene.loh@oracle.com \
    --cc=dtrace-devel@oss.oracle.com \
    --cc=dtrace@lists.linux.dev \
    /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