[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Feed on specific topic (public-inbox?)
From: |
zimoun |
Subject: |
Feed on specific topic (public-inbox?) |
Date: |
Fri, 03 Jun 2022 10:22:36 +0200 |
Hi,
On Thu, 02 Jun 2022 at 21:35, Luis Felipe <luis.felipe.la@protonmail.com> wrote:
> As for reviewing patches or just taking a look at reported issues
> against parts of Guix one is interested, it would be easier if there
> were some kind of subscription system. Say, I'd like to subscribe to
> issues on Python packages, Spanish translation, and guix-artwork. I
> know this kind of subscription thing has been mentioned before,
> though.
As discussed in «Incentives for review» [1], using public-inbox, you can
filter using «dfn: match filename from diff» or even write more complex
queries [2]. For instance, read from your browser,
https://yhetil.org/guix-patches/?q=dfn:python
And you can even follow a feed, for instance:
https://yhetil.org/guix-patches/?q=dfn:python&x=A
Note that recent ’public-inbox’ comes from with the tool ’lei’. This
tool ’lei’ allows to query a public-inbox server and then fetch some
filtered messages to use it locally. Currently, the Guix package is at
1.6 and it requires an update at 1.7; discussed here [3]. In this
message [4], you can find some Emacs workflow using public-inbox.
For guix-artwork, as a whole, I do not know what would be the best
query.
What is missing from Mumi is the use of Message-ID for an easy
referencing between the email tools, as discussed in [5].
As we discussed once, maybe it would help to have an “official“
public-inbox instance for the Guix project. For instance, Org folks
uses a public-inbox instance [6] and switched 2 years ago [7].
>From my point of view, public-inbox would fix some annoyance about the
“email workflow”. Now the question is: who help in the maintenance? :-)
1: <https://yhetil.org/guix/87mtn56mzg.fsf_-_@inria.fr>
2: <https://public-inbox.org/meta/_/text/help/>
3: <https://yhetil.org/guix/877d6w96by.fsf@kolabnow.com>
4: <https://yhetil.org/guix/87bkwf956h.fsf@gmail.com>
5: <https://yhetil.org/guix/86sgbhz3fe.fsf@gmail.com>
6: <https://list.orgmode.org/orgmode/87ilyjuoed.fsf@bzg.fr/>
7: <https://list.orgmode.org/orgmode/87k10mt0n6.fsf@bzg.fr/>
Cheers,
simon
- Re: On commit access, patch review, and remaining healthy, (continued)
- Re: On commit access, patch review, and remaining healthy, Efraim Flashner, 2022/06/07
- Re: On commit access, patch review, and remaining healthy, Ludovic Courtès, 2022/06/07
- Re: On commit access, patch review, and remaining healthy, Efraim Flashner, 2022/06/08
- Re: On commit access, patch review, and remaining healthy, Ludovic Courtès, 2022/06/08
- Re: On commit access, patch review, and remaining healthy, Hartmut Goebel, 2022/06/20
- Re: On commit access, patch review, and remaining healthy, zimoun, 2022/06/21
- Re: On commit access, patch review, and remaining healthy, Munyoki Kilyungi, 2022/06/22
Re: On commit access, patch review, and remaining healthy, Pier-Hugues Pellerin, 2022/06/02
Re: On commit access, patch review, and remaining healthy, Luis Felipe, 2022/06/02
- Feed on specific topic (public-inbox?),
zimoun <=
Re: On commit access, patch review, and remaining healthy, Arun Isaac, 2022/06/06
- Re: On commit access, patch review, and remaining healthy, Ludovic Courtès, 2022/06/06
- Re: On commit access, patch review, and remaining healthy, zimoun, 2022/06/07
- Re: On commit access, patch review, and remaining healthy, Giovanni Biscuolo, 2022/06/08
- Re: On commit access, patch review, and remaining healthy, zimoun, 2022/06/14
- Re: On commit access, patch review, and remaining healthy, Arun Isaac, 2022/06/15
- Re: On commit access, patch review, and remaining healthy, Ludovic Courtès, 2022/06/15
- Re: On commit access, patch review, and remaining healthy, Paul Jewell, 2022/06/19
- Re: On commit access, patch review, and remaining healthy, Arun Isaac, 2022/06/20