public inbox for dtrace@lists.linux.dev
 help / color / mirror / Atom feed
From: Kris Van Hees <kris.van.hees@oracle.com>
To: eugene.loh@oracle.com
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH] Add more Orabugs to dtrace.spec
Date: Mon, 27 Oct 2025 13:38:33 -0400	[thread overview]
Message-ID: <aP+uGR+uKdotn+wp@oracle.com> (raw)
In-Reply-To: <20251025191751.32158-1-eugene.loh@oracle.com>

On Sat, Oct 25, 2025 at 03:17:51PM -0400, eugene.loh@oracle.com wrote:
> From: Eugene Loh <eugene.loh@oracle.com>
> 
> Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
> ---
>  dtrace.spec | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/dtrace.spec b/dtrace.spec
> index c0183cb5f..a4f3ed774 100644
> --- a/dtrace.spec
> +++ b/dtrace.spec
> @@ -242,8 +242,10 @@ systemctl start dtprobed || :
>  - Error injection via return() action.  (Kris Van Hees)
>  - Improved string handling.  (Kris Van Hees)
>  - Various bug fixes.  (Eugene Loh, Kris Van Hees)
> +  [Orabug: 37994729, 38249511]
>  - Various testsuite fixes and improvements.
>    (Nick Alcock, Eugene Loh, Alan Maguire, Kris Van Hees)
> +  [Orabug: 28763074, 37459289]

It would be preferred if the Orabug numbers are associated with a changelog
entry that refers to the issue the bug fix resolves, in a generic fashion (i.e.
limited to the issue in the codebase).  The Orabug mentioned with Various
bug fixes and Various testsuite fixes usually is a placeholder Orabug that
captures the entirety of the release.

>  * Tue Jun 10 2025 Kris Van Hees <kris.van.hees@oracle.com> - 2.0.3-1
>  - This is only released on OL10.
> @@ -334,7 +336,7 @@ systemctl start dtprobed || :
>  - Fix dtprobed to support DOF that exceeds 64KiB. (Nick Alcock)
>    [Orabug: 35411920]
>  - Do not modify input files with dtrace -G if unchanged. (Steven Sistare)
> -  [Orbug: 35417184]
> +  [Orabug: 35417184]

Good catch.

>  - Various testsuite fixes and improvements.
>    (Nick Alcock, Eugene Loh, Kris Van Hees) [Orabug: 35435195]
>  - Various code improvements.  (Nick Alcock, Eugene Loh, Kris Van Hees)
> -- 
> 2.47.3
> 

      reply	other threads:[~2025-10-27 17:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-25 19:17 [PATCH] Add more Orabugs to dtrace.spec eugene.loh
2025-10-27 17:38 ` Kris Van Hees [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=aP+uGR+uKdotn+wp@oracle.com \
    --to=kris.van.hees@oracle.com \
    --cc=dtrace-devel@oss.oracle.com \
    --cc=dtrace@lists.linux.dev \
    --cc=eugene.loh@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