[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Guix Days: Patch flow discussion
From: |
Maxim Cournoyer |
Subject: |
Re: Guix Days: Patch flow discussion |
Date: |
Sun, 11 Feb 2024 11:38:02 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Hi,
Kyle Meyer <kyle@kyleam.com> writes:
> Hi Ricardo,
>
> Ricardo Wurmus writes:
>
>> Hi Josselin,
>
>>> They both can co-exist with debbugs, and for now the patchwork instance
>>> of QA is not usable for status tracking (because it is not meant to be
>>> used as such for now). One can already use both of them, but using both
>>> supercedes debbugs, and gets rid of its limitations. I've been using
>>> b4/lei with the yhetil public-inbox instance, with piem.el as an
>>> interface, and it's really useful. With a properly configured b4, one
>>> could simply run `b4 shazam some-msg-id` and it would automatically
>>> apply the corresponding patchset.
>>
>> I’m interested in adopting this workflow. Where can I find more
>> information on how to configure this?
>
> In 889a6204f8 (doc: Add some guidelines for reviewing, 2023-11-07),
> Maxim added some b4 configuration to Guix's etc/git/gitconfig that
> points at yhetil.org. With that setup, running 'b4 shazam MESSAGE-ID'
> from a Guix checkout should work.
Indeed! It should perhaps be more prominently documented, probably as
an new 'Reviewing patch work flows' section in the Guix Cookbook that
could be linked from our already lengthy Contributions section.
'b4 shazam' is probably the most trouble-free way to apply patches; it
even selects the latest revision it finds in the issue thread. To make
finding a message-id easier, I've also recently added a 'Copy
Message-ID' button to the Mumi interface; try it visiting any issue,
e.g. <https://issues.guix.gnu.org/68990>. The message-id of any message
can be easily copied to your clipboard via the new button. From your
Guix checkout, you'd then run:
--8<---------------cut here---------------start------------->8---
$ b4 shazam 'cover.1707383694.git.h.goebel@crazy-compilers.com'
Looking up
https://yhetil.org/guix/cover.1707383694.git.h.goebel@crazy-compilers.com
Grabbing thread from
yhetil.org/guix/cover.1707383694.git.h.goebel@crazy-compilers.com/t.mbox.gz
Checking for newer revisions
Grabbing search results from lore.kernel.org
Nothing matching that query.
Analyzing 29 messages in the thread
---
[PATCH 1/28] gnu: Add ruby-test-unit-ruby-core.
[PATCH 2/28] gnu: Add ruby-excon.
[PATCH 3/28] gnu: Add ruby-ipaddr.
[PATCH 4/28] gnu: Add ruby-net-ftp.
[PATCH 5/28] gnu: Add ruby-fake-ftp.
[PATCH 6/28] gnu: Add ruby-net-sftp.
[PATCH 7/28] gnu: Add ruby-net-telnet.
[PATCH 8/28] gnu: Add ruby-pairing-heap.
[PATCH 9/28] gnu: Add ruby-stringio.
[PATCH 10/28] gnu: Add ruby-stream.
[PATCH 11/28] gnu: Add ruby-rgl.
[PATCH 12/28] gnu: Add ruby-sfl.
[PATCH 13/28] gnu: Add ruby-specinfra.
[PATCH 14/28] gnu: Add ruby-serverspec.
[PATCH 15/28] gnu: Add ruby-time.
[PATCH 16/28] gnu: Add ruby-google-protobuf.
[PATCH 17/28] gnu: Add ruby-googleapis-common-protos-types.
[PATCH 18/28] gnu: Add ruby-grpc.
[PATCH 19/28] gnu: Add ruby-vagrant-cloud.
[PATCH 20/28] gnu: Add ruby-vagrant-spec.
[PATCH 21/28] gnu: Add ruby-vagrant-spec-helper-basic.
[PATCH 22/28] gnu: Add ruby-hashicorp-checkpoint.
[PATCH 23/28] gnu: ruby-childprocess: Update to 4.1.0.
[PATCH 24/28] gnu: Add ruby-libvirt.
[PATCH 25/28] gnu: Add ruby-fog-core.
[PATCH 26/28] gnu: Add ruby-fog-json.
[PATCH 27/28] gnu: Add ruby-fog-xml.
[PATCH 28/28] gnu: Add ruby-fog-libvirt.
---
Total patches: 28
---
Base: using specified base-commit a4464bd0975c811f18af98f69032b29bddda5b81
Application de gnu: Add ruby-test-unit-ruby-core.
Application de gnu: Add ruby-excon.
Application de gnu: Add ruby-ipaddr.
Application de gnu: Add ruby-net-ftp.
Application de gnu: Add ruby-fake-ftp.
Application de gnu: Add ruby-net-sftp.
Application de gnu: Add ruby-net-telnet.
Application de gnu: Add ruby-pairing-heap.
Application de gnu: Add ruby-stringio.
Application de gnu: Add ruby-stream.
Application de gnu: Add ruby-rgl.
Application de gnu: Add ruby-sfl.
Application de gnu: Add ruby-specinfra.
Application de gnu: Add ruby-serverspec.
Application de gnu: Add ruby-time.
Application de gnu: Add ruby-google-protobuf.
Application de gnu: Add ruby-googleapis-common-protos-types.
Application de gnu: Add ruby-grpc.
Application de gnu: Add ruby-vagrant-cloud.
Application de gnu: Add ruby-vagrant-spec.
Application de gnu: Add ruby-vagrant-spec-helper-basic.
Application de gnu: Add ruby-hashicorp-checkpoint.
Application de gnu: ruby-childprocess: Update to 4.1.0.
Application de gnu: Add ruby-libvirt.
Application de gnu: Add ruby-fog-core.
Application de gnu: Add ruby-fog-json.
Application de gnu: Add ruby-fog-xml.
Application de gnu: Add ruby-fog-libvirt.
--8<---------------cut here---------------end--------------->8---
and done!
--
Thanks,
Maxim
- Re: Guix Days: Patch flow discussion, (continued)
- Re: Guix Days: Patch flow discussion, Clément Lassieur, 2024/02/11
- Re: Guix Days: Patch flow discussion, Josselin Poiret, 2024/02/12
- Re: Guix Days: Patch flow discussion, Clément Lassieur, 2024/02/12
- Re: Guix Days: Patch flow discussion, Felix Lechner, 2024/02/12
- Re: Guix Days: Patch flow discussion, Josselin Poiret, 2024/02/13
- Re: Guix Days: Patch flow discussion, Felix Lechner, 2024/02/13
- Re: Guix Days: Patch flow discussion, Josselin Poiret, 2024/02/14
- Re: Guix Days: Patch flow discussion, Clément Lassieur, 2024/02/07
- Re: Guix Days: Patch flow discussion, Ricardo Wurmus, 2024/02/07
- Re: Guix Days: Patch flow discussion, Kyle Meyer, 2024/02/07
- Re: Guix Days: Patch flow discussion,
Maxim Cournoyer <=
- Re: Guix Days: Patch flow discussion, Simon Tournier, 2024/02/15
- Re: Guix Days: Patch flow discussion, Josselin Poiret, 2024/02/15
- Re: Guix Days: Patch flow discussion, Simon Tournier, 2024/02/15
- Re: Guix Days: Patch flow discussion, Clément Lassieur, 2024/02/15
- Re: Guix Days: Patch flow discussion, Clément Lassieur, 2024/02/15
- Re: Guix Days: Patch flow discussion, Felix Lechner, 2024/02/15
- Re: Guix Days: Patch flow discussion, Simon Tournier, 2024/02/15
- Re: Guix Days: Patch flow discussion, Maxim Cournoyer, 2024/02/16
- Re: Guix Days: Patch flow discussion, Simon Tournier, 2024/02/15
- Re: Guix Days: Patch flow discussion, Clément Lassieur, 2024/02/15