From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Greg Kurz <groug@kaod.org>, Andrey Erokhin <language.lawyer@gmail.com>
Subject: Re: [PATCH] hw/9pfs: Follow native symlinks when security-model=mapped
Date: Sat, 22 Nov 2025 13:23:29 +0100 [thread overview]
Message-ID: <4694008.LvFx2qVVIh@weasel> (raw)
In-Reply-To: <f5fee3f9-9075-4d73-96b2-5d026500e295@gmail.com>
On Friday, 21 November 2025 19:32:14 CET Andrey Erokhin wrote:
> On 21/11/2025 17:20, Christian Schoenebeck wrote:
> > Andrey, just some minor issues from my side below:
> >
> > Git commit log message should not exceed 76 characters per line.
>
> TBH, I'm not used to sending patches by git, it was just an e-mail message,
> not a commit message
NP. You can use whatever you want (git send-email, any standard email client,
a script). However patches are automatically applied from this mailing list,
so the leading sentences of your email *is* the git commit log message.
> >> QEMU issues:
> >> https://gitlab.com/qemu-project/qemu/-/issues/173 (from
> >> https://bugs.launchpad.net/qemu/+bug/1831354)
> >> https://gitlab.com/qemu-project/qemu/-/issues/3088 (dup of the first one)
> >
> > This should be:
> >
> > Resolves: https://gitlab.com/qemu-project/qemu/-/issues/173
>
> Fixed in the attached patch. Or should I start a new [PATCH v2] thread?
Please resend with [PATCH v2] in the subject. Patches should always be inline
in the email, not as an attachment, and new versions should be top posted
(i.e. not In-Reply-To v1 email).
/Christian
prev parent reply other threads:[~2025-11-22 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 13:01 [PATCH] hw/9pfs: Follow native symlinks when security-model=mapped Andrey Erokhin
2025-11-21 12:20 ` Christian Schoenebeck
2025-11-21 18:32 ` Andrey Erokhin
2025-11-22 12:23 ` Christian Schoenebeck [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=4694008.LvFx2qVVIh@weasel \
--to=qemu_oss@crudebyte.com \
--cc=groug@kaod.org \
--cc=language.lawyer@gmail.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.