public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 5/5] pesto: Introduce stub configuration interface and tool
Date: Wed, 18 Mar 2026 12:13:04 +1100	[thread overview]
Message-ID: <abn8IB4IWKfEzuFl@zatzit> (raw)
In-Reply-To: <abn4lnRAU_CwhN_-@zatzit>

[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]

On Wed, Mar 18, 2026 at 11:57:58AM +1100, David Gibson wrote:
> On Tue, Mar 17, 2026 at 10:36:29AM +0100, Stefano Brivio wrote:
> > On Tue, 17 Mar 2026 11:48:50 +1100
> > David Gibson <david@gibson.dropbear.id.au> wrote:
> > 
> > > On Tue, Mar 17, 2026 at 01:02:46AM +0100, Stefano Brivio wrote:
> > >
> > > > [...]
> > > >
> > > > Note: we should remember to tackle your own comments from
> > > > <aYqw6M2G9n-tv9Qm@zatzit>, eventually (not necessarily now, but fd_conf
> > > > just reminded me).  
> > > 
> > > Uh, don't remember what that mail was and I'm not immediately sure how
> > > to search for it based on message-id.
> > 
> > No need to search, we use public-inbox, so:
> > 
> >   https://archives.passt.top/passt-dev/aYqw6M2G9n-tv9Qm@zatzit
> > 
> > (or, at least in claws-mail, select "Extended" in the search box, then
> > 'i MSG_ID').
> 
> I was including techniques like that under the broad category of
> "search".  I assumed there was an easy way, I just didn't know what it
> was.
> 
> I think I addressed most of my comments there already, but I should go
> back through and double check.

Less than I thought, as it turns out, but I've been back through them
all and updated accordingly.

-- 
David Gibson (he or they)	| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you, not the other way
				| around.
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-03-18  1:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16  5:46 [PATCH 0/5] RFC: Stub dynamic update implementation David Gibson
2026-03-16  5:46 ` [PATCH 1/5] Makefile: Use $^ to avoid duplication in static checker rules David Gibson
2026-03-16  5:46 ` [PATCH 2/5] doc: Fix formatting of (DEPRECATED) notes in man page David Gibson
2026-03-16  5:46 ` [PATCH 3/5] pif: Remove unused PIF_NAMELEN David Gibson
2026-03-16  5:46 ` [PATCH 4/5] treewide: Spell ASSERT() as assert() David Gibson
2026-03-17  0:02   ` Stefano Brivio
2026-03-17  0:39     ` David Gibson
2026-03-17  9:36       ` Stefano Brivio
2026-03-18  0:52         ` David Gibson
2026-03-16  5:46 ` [PATCH 5/5] pesto: Introduce stub configuration interface and tool David Gibson
2026-03-17  0:02   ` Stefano Brivio
2026-03-17  0:48     ` David Gibson
2026-03-17  9:36       ` Stefano Brivio
2026-03-18  0:57         ` David Gibson
2026-03-18  1:13           ` David Gibson [this message]
2026-03-17  0:02 ` [PATCH 0/5] RFC: Stub dynamic update implementation Stefano Brivio

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=abn8IB4IWKfEzuFl@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    --cc=sbrivio@redhat.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.
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).