From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH] .skills: fix broken links from .claude/.gemini dirs
Date: Thu, 12 Nov 2026 17:36:34 +0000 [thread overview]
Message-ID: <avX5IqyPc8PkF_FH@redhat.com> (raw)
In-Reply-To: <20261013134904.1012071-1-berrange@redhat.com>
ping: any reviews/acks for this trivial fix
On Tue, Oct 13, 2026 at 02:49:04PM +0100, Daniel P. Berrangé wrote:
> The symlinks were not traversing up to the parent dir.
>
> Fixes: 3e9fe057ae (agents: Add a skill for finding your way around QEMU)
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> .claude/skills | 2 +-
> .gemini/skills | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/.claude/skills b/.claude/skills
> index a7540c24423..2b7a412b8fa 120000
> --- a/.claude/skills
> +++ b/.claude/skills
> @@ -1 +1 @@
> -.agents/skills/
> \ No newline at end of file
> +../.agents/skills
> \ No newline at end of file
> diff --git a/.gemini/skills b/.gemini/skills
> index a7540c24423..2b7a412b8fa 120000
> --- a/.gemini/skills
> +++ b/.gemini/skills
> @@ -1 +1 @@
> -.agents/skills/
> \ No newline at end of file
> +../.agents/skills
> \ No newline at end of file
> --
> 2.56.0
>
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
prev parent reply other threads:[~2026-11-12 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 13:49 [PATCH] .skills: fix broken links from .claude/.gemini dirs Daniel P. Berrangé
2026-11-12 17:36 ` Daniel P. Berrangé [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=avX5IqyPc8PkF_FH@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.