From: zhanxusheng1024-os <noreply@github.com>
To: dtrace@lists.linux.dev
Subject: [oracle/dtrace] 61fea6: llm: fix newline escape in the SKILL.md script ske...
Date: Fri, 28 Aug 2026 10:52:31 -0700 [thread overview]
Message-ID: <oracle/dtrace/push/refs/heads/dev-queue/30c9c2-61fea6@github.com> (raw)
Branch: refs/heads/dev-queue
Home: https://github.com/oracle/dtrace
Commit: 61fea621160ea4b6302874c62a723da105b44883
https://github.com/oracle/dtrace/commit/61fea621160ea4b6302874c62a723da105b44883
Author: Zhan Xusheng <zhanxusheng1024@gmail.com>
Date: 2026-08-28 (Fri, 28 Aug 2026)
Changed paths:
M llm/SKILL.md
Log Message:
-----------
llm: fix newline escape in the SKILL.md script skeleton
The skeleton's BEGIN and ERROR clauses use "\\n" where "\n" is meant.
In a D string literal that is an escaped backslash followed by 'n', so
printf() emits a stray backslash instead of a newline.
Agents copy the skeleton verbatim, and "\\n" is a valid literal, so the
'dtrace -e' check prescribed in the same file does not catch it.
Every other D snippet in the tree uses a single backslash.
Assisted-by: Kiro:claude-opus-4.8
Signed-off-by: Zhan Xusheng <zhanxusheng@xiaomi.com>
Reviewed-by: Kris Van Hees <kris.van.hees@oracle.com>
To unsubscribe from these emails, change your notification settings at https://github.com/oracle/dtrace/settings/notifications
next reply other threads:[~2026-08-28 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 17:52 zhanxusheng1024-os [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-28 17:52 [oracle/dtrace] 61fea6: llm: fix newline escape in the SKILL.md script ske zhanxusheng1024-os
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=oracle/dtrace/push/refs/heads/dev-queue/30c9c2-61fea6@github.com \
--to=noreply@github.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