From: Stefano Brivio <sbrivio@redhat.com>
To: Max Chernoff <git@maxchernoff.ca>
Cc: Danish Prakash <contact@danishpraka.sh>,
passt-dev@passt.top, pholzing@redhat.com
Subject: Re: [PATCH v2] contrib/selinux: use regex instead of SELinux template
Date: Wed, 5 Nov 2025 16:31:37 +0100 [thread overview]
Message-ID: <20251105163137.424a6537@elisabeth> (raw)
In-Reply-To: <b2e183a39431c8dd3855bf3067814bea380aba3b.camel@maxchernoff.ca>
On Wed, 05 Nov 2025 03:28:22 -0700
Max Chernoff <git@maxchernoff.ca> wrote:
> Hi Stefano,
>
> On Tue, 2025-11-04 at 22:13 +0100, Stefano Brivio wrote:
> > Max, thanks for testing and reviewing, I took the liberty to translate
> > your comments into Tested-by: and Reviewed-by: tags as they clearly
> > seemed to indicate that.
>
> Ah, thanks for that! I'm still fairly new to the patch-on-a-mailing-list
> workflow, so is there something that I should have done differently?
We use pretty much the same tags as the Linux kernel does:
https://docs.kernel.org/process/submitting-patches.html#using-reported-by-tested-by-reviewed-by-suggested-by-and-fixes
(except we only use Link:, not Closes:) which are nice because they're
machine-readable, so one could use, say, for instance, a script like:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/scripts/get_maintainer.pl
to Cc: you automatically on a patch if you often reviewed or tested
the code or file affected by it.
So, here, you could have simply replied with:
Reviewed-by: Max Chernoff <git@maxchernoff.ca>
Tested-by: Max Chernoff <git@maxchernoff.ca>
to unequivocally state what you did with that submission.
Now, passt is small enough that we don't really have much of a use for
that at the moment, but it still sounds like a good idea in general,
also to future-proof things. It's also small enough that I can add /
fix tags as I merge patches without much fuss.
And yes, this should also be added to the new CONTRIBUTING.md file, I
have a growing list of small items to add and I'll do that in a batch
at some point. :)
--
Stefano
next prev parent reply other threads:[~2025-11-05 15:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 7:40 [PATCH] contrib/selinux: use regex instead of non-standard bash macro Danish Prakash
2025-10-16 8:21 ` Stefano Brivio
2025-10-16 10:56 ` Max Chernoff
2025-10-27 8:49 ` Danish Prakash
2025-10-27 9:07 ` Stefano Brivio
2025-10-27 9:41 ` Max Chernoff
2025-10-28 6:28 ` Danish Prakash
2025-10-28 23:17 ` Stefano Brivio
2025-10-30 8:20 ` [PATCH v2] contrib/selinux: use regex instead of SELinux template Danish Prakash
2025-10-30 8:37 ` [PATCH] contrib/selinux: use regex instead of non-standard bash macro Danish Prakash
2025-10-30 8:43 ` Stefano Brivio
2025-10-30 10:06 ` Stefano Brivio
2025-10-30 10:50 ` Danish Prakash
2025-10-30 10:49 ` [PATCH v2] contrib/selinux: use regex instead of SELinux template Danish Prakash
2025-11-04 6:48 ` Max Chernoff
2025-11-04 21:13 ` Stefano Brivio
2025-11-05 10:28 ` Max Chernoff
2025-11-05 15:31 ` Stefano Brivio [this message]
2025-11-06 12:09 ` Max Chernoff
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=20251105163137.424a6537@elisabeth \
--to=sbrivio@redhat.com \
--cc=contact@danishpraka.sh \
--cc=git@maxchernoff.ca \
--cc=passt-dev@passt.top \
--cc=pholzing@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).