From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Laurent Vivier" <lvivier@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
hi@alyssa.is, "Michael Roitzsch" <reactorcontrol@icloud.com>,
"Will Cohen" <wwcohen@gmail.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Keno Fischer" <keno@juliacomputing.com>,
"Greg Kurz" <groug@kaod.org>
Subject: Re: [PATCH v9 09/11] 9p: darwin: Implement compatibility for mknodat
Date: Mon, 28 Feb 2022 16:45:33 +0100 [thread overview]
Message-ID: <3768063.azJo349jol@silver> (raw)
In-Reply-To: <CAFEAcA_1-xK9u3jsZ0MyCEsQOsr3Dp0bHRtyXYDj7CDWw4-D8Q@mail.gmail.com>
On Montag, 28. Februar 2022 15:06:07 CET Peter Maydell wrote:
> On Mon, 28 Feb 2022 at 13:58, Christian Schoenebeck
>
> <qemu_oss@crudebyte.com> wrote:
> > On Montag, 28. Februar 2022 14:36:30 CET Thomas Huth wrote:
> > > For lines less than 90 characters, it's just a warning, and I think it's
> > > ok
> > > in such cases to keep it longer than 80 characters, if the result of
> > > breaking it up would look more awkward otherwise.
> > >
> > > Thomas
> >
> > This doesn't look awkward to me:
> > error_report_once(
> >
> > "pthread_fchdir_np() is not available on this version of
> > macOS"
> >
> > );
>
> I think that looks pretty strange, though "git grep -A3 -- '($'" does show
> other examples of doing it that way. I'd favour leaving it as a single
> line, which the style guide allows ("better to have an 85 character line
> than one which is awkwardly wrapped").
>
> Personally I would favour just not warning at all about the more-than-80
> less-than-90 lines case: it mostly tends to produce discussions like this
> one and people preferring to break lines that would be better unbroken.
> I know not everybody agrees with that, though.
>
> -- PMM
There is a practical reason for keeping things <80 chars: some email clients
like mine do awkward attempts to constrain lines to 80 chars in replies, which
I then always have to manually fix for the quoted diff being readable again.
E.g. in this case it screwed it like this:
> +int qemu_mknodat(int dirfd, const char *filename, mode_t mode, dev_t dev)
> +{
> + int preserved_errno, err;
> + if (!pthread_fchdir_np) {
> + error_report_once("pthread_fchdir_np() not available on this
> version of macOS"); + return -ENOTSUP;
> + }
> + if (pthread_fchdir_np(dirfd) < 0) {
> + return -1;
> + }
Anyway, I leave this as-is then, as I seem to have a minority opinion.
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2022-02-28 15:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 22:35 [PATCH v9 00/11] 9p: Add support for darwin Will Cohen
2022-02-27 22:35 ` [PATCH v9 01/11] 9p: linux: Fix a couple Linux assumptions Will Cohen
2022-02-27 22:35 ` [PATCH v9 02/11] 9p: Rename 9p-util -> 9p-util-linux Will Cohen
2022-02-27 22:35 ` [PATCH v9 03/11] 9p: darwin: Handle struct stat(fs) differences Will Cohen
2022-02-27 22:35 ` [PATCH v9 04/11] 9p: darwin: Handle struct dirent differences Will Cohen
2022-02-27 22:35 ` [PATCH v9 05/11] 9p: darwin: Ignore O_{NOATIME, DIRECT} Will Cohen
2022-02-27 22:35 ` [PATCH v9 06/11] 9p: darwin: Move XATTR_SIZE_MAX->P9_XATTR_SIZE_MAX Will Cohen
2022-02-27 22:35 ` [PATCH v9 07/11] 9p: darwin: *xattr_nofollow implementations Will Cohen
2022-02-27 22:35 ` [PATCH v9 08/11] 9p: darwin: Compatibility for f/l*xattr Will Cohen
2022-02-27 22:35 ` [PATCH v9 09/11] 9p: darwin: Implement compatibility for mknodat Will Cohen
2022-02-28 13:20 ` Christian Schoenebeck
2022-02-28 13:36 ` Thomas Huth
2022-02-28 13:51 ` Christian Schoenebeck
2022-02-28 14:06 ` Peter Maydell
2022-02-28 15:45 ` Christian Schoenebeck [this message]
2022-02-28 13:37 ` Will Cohen
2022-02-28 13:41 ` Greg Kurz
2022-04-08 13:52 ` Christian Schoenebeck
2022-04-08 15:00 ` Greg Kurz
2022-04-12 12:19 ` Christian Schoenebeck
2022-02-27 22:35 ` [PATCH v9 10/11] 9p: darwin: Adjust assumption on virtio-9p-test Will Cohen
2022-02-27 22:35 ` [PATCH v9 11/11] 9p: darwin: meson: Allow VirtFS on Darwin Will Cohen
2022-02-28 13:11 ` Christian Schoenebeck
2022-02-28 13:43 ` Will Cohen
2022-03-01 19:25 ` [PATCH v9 00/11] 9p: Add support for darwin Christian Schoenebeck
2022-03-01 20:09 ` Will Cohen
2022-03-02 18:15 ` Christian Schoenebeck
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=3768063.azJo349jol@silver \
--to=qemu_oss@crudebyte.com \
--cc=f4bug@amsat.org \
--cc=groug@kaod.org \
--cc=hi@alyssa.is \
--cc=keno@juliacomputing.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=reactorcontrol@icloud.com \
--cc=thuth@redhat.com \
--cc=wwcohen@gmail.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;
as well as URLs for NNTP newsgroup(s).