From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top, Laurent Vivier <lvivier@redhat.com>
Subject: Re: [PATCH 0/5] Settings for Zed editor and minor fixups
Date: Tue, 08 Sep 2026 17:01:53 +0200 (CEST) [thread overview]
Message-ID: <20260908170152.3da856ff@elisabeth> (raw)
In-Reply-To: <20260821050403.170891-1-david@gibson.dropbear.id.au>
On Fri, 21 Aug 2026 15:03:58 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> I've been playing with the Zed editor again. It's default settings
> don't quite match passt's style, so add a config file to make it do
> the right thing. Also update some of the config for clangd to
> suppress bogus warnings the way Zed invokes it.
>
> Between them these also found a handful of minor but real code warts,
> so fix those, too.
>
> David Gibson (5):
> clangd: Add _GNU_SOURCE to default clangd options
> util: Eliminate a stray trailing whitespace
> util: Add missing O_CLOEXEC for !HAS_GETRANDOM path
> util, pasta: Remove some unneeded #includes
> Add Zed editor settings
Series applied as well.
--
Stefano
prev parent reply other threads:[~2026-09-08 15:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 5:03 David Gibson
2026-08-21 5:03 ` [PATCH 1/5] clangd: Add _GNU_SOURCE to default clangd options David Gibson
2026-08-21 12:50 ` Laurent Vivier
2026-08-21 5:04 ` [PATCH 2/5] util: Eliminate a stray trailing whitespace David Gibson
2026-08-21 12:52 ` Laurent Vivier
2026-08-21 5:04 ` [PATCH 3/5] util: Add missing O_CLOEXEC for !HAS_GETRANDOM path David Gibson
2026-08-21 12:56 ` Laurent Vivier
2026-08-21 5:04 ` [PATCH 4/5] util, pasta: Remove some unneeded #includes David Gibson
2026-08-21 13:05 ` Laurent Vivier
2026-08-21 5:04 ` [PATCH 5/5] Add Zed editor settings David Gibson
2026-09-08 15:01 ` Stefano Brivio [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=20260908170152.3da856ff@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).