From: Vagrant Cascadian <vagrant@debian.org>
To: Simon Tournier <zimon.toutoune@gmail.com>, guix-devel@gnu.org
Subject: Re: Some team related thoughts and questions...
Date: Tue, 10 Jan 2023 15:32:20 -0800 [thread overview]
Message-ID: <87pmbmm0e3.fsf@contorta> (raw)
In-Reply-To: <875ydfzzpl.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1960 bytes --]
On 2023-01-09, Simon Tournier wrote:
> On ven., 06 janv. 2023 at 10:42, Vagrant Cascadian <vagrant@debian.org> wrote:
>> More I wanted to look through the patch text rather than the package
>> descriptions. It would ideally catch things like "reproducible" or
>> "deterministic" in comments in patches as well as git commit summary.
>
> Well, IIUC, your point would be to have teams based on “topic“ referred
> by search term in patches. Why not, although it is far to be
> implemented, I guess. ;-)
Sure, it is wishing for a feature, on the hopes that someone more savvy
with parens sees the value and implements it. :)
> BTW, I would recommend to give a look at lei [1,2] from the Guix package
> public-inbox. For instance, over the last 12 months, all patches
> containing the terms ’r-build-system’ and ’reproducible’,
>
> 1. Extract from a public-inbox instance:
>
> guix shell public-inbox \
> -- lei q --threads --dedupe=mid \
> -I https://yhetil.org/guix-patches/ -o /tmp/Mail/patches \
> 'dfn:gnu/packages AND b:r-build-system AND b:reproducible AND rt:12.months.ago..'
>
> 2. Read it with a mail reader support Maildir:
>
> guix shell neomutt -- neomutt -f /tmp/Mail/patches
>
>
> where
>
> dfn: match filename from diff
> b: match within message body, including text attachments
> rt: match date-time range, git "approxidate" formats supported
> Open-ended ranges such as `d:last.week..' and `d:..2.days.ago'
> are supported
Thanks for the examples! I have tried to wrap my head around
public-inbox and related tooling, as it seems extremely
useful. Hopefully this gets me into actually using it. :)
Though using public-inbox is obviously working at it from the other end,
not getting CCed on things but having to rummage through the heap of
patches to find them. :)
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2023-01-10 23:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 6:11 Some team related thoughts and questions Vagrant Cascadian
2023-01-06 17:14 ` Simon Tournier
2023-01-06 18:42 ` Vagrant Cascadian
2023-01-09 11:58 ` Simon Tournier
2023-01-10 23:32 ` Vagrant Cascadian [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmbmm0e3.fsf@contorta \
--to=vagrant@debian.org \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).