From: Lars-Dominik Braun <lars@6xq.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, Kyle Meyer <kyle@kyleam.com>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: Re: Formalizing teams
Date: Wed, 29 Dec 2021 22:04:15 +0100 [thread overview]
Message-ID: <YczNTxe4Z5Njjanq@noor.fritz.box> (raw)
In-Reply-To: <87lf04ip1e.fsf@elephly.net>
Hi Ricardo,
> FWIW, mumi also lets you search patches as all contents are indexed:
> https://issues.guix.gnu.org/search?query=%22%28gnu+packages+python-web%29%22+is%3Aopen+tag%3Apatch
thanks, I didn’t think about that. I tried searching
for python-build-system, but not all patches – especially
trivial ones – include enough context (for example
https://issues.guix.gnu.org/52595). Searching for files yields too many
packages, since Python packages are scattered across dozens of files
(e.g. gnu/packages/music.scm).
So unfortunately it doesn’t solve my problem. The only reasonable
thing to do right now seems to be setting up package name based filters,
because commit messages have a format known in advance.
Cheers,
Lars
next prev parent reply other threads:[~2021-12-29 21:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 15:46 Formalizing teams Ludovic Courtès
2021-12-22 16:04 ` Jack Hill
2021-12-22 16:22 ` indieterminacy
2021-12-22 19:43 ` Filip Łajszczak
2022-01-03 15:09 ` Ludovic Courtès
2021-12-27 5:17 ` Maxim Cournoyer
2021-12-28 10:52 ` Lars-Dominik Braun
2021-12-28 15:44 ` Kyle Meyer
2021-12-28 18:03 ` Ricardo Wurmus
2021-12-29 21:04 ` Lars-Dominik Braun [this message]
2021-12-28 14:44 ` Ricardo Wurmus
2021-12-29 9:05 ` Efraim Flashner
2022-01-03 15:22 ` Ludovic Courtès
2022-01-03 15:57 ` Ricardo Wurmus
2022-01-04 22:35 ` adriano
2022-03-31 21:15 ` david larsson
2022-04-01 9:14 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2021-12-23 15:13 Blake Shaw
2021-12-23 21:51 ` Jonathan McHugh
2021-12-24 12:23 ` Hartmut Goebel
2021-12-24 15:37 ` indieterminacy
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=YczNTxe4Z5Njjanq@noor.fritz.box \
--to=lars@6xq.net \
--cc=guix-devel@gnu.org \
--cc=kyle@kyleam.com \
--cc=maxim.cournoyer@gmail.com \
--cc=rekado@elephly.net \
/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).