From: Richard Sent <richard@freakingpenguin.com>
To: Nicolas Graves via "Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org>
Cc: zimoun.toutoune@gmail.com, "Ludovic Courtès" <ludo@gnu.org>,
"Nicolas Graves" <ngraves@ngraves.fr>
Subject: Re: (almost) deterministic patchsets
Date: Fri, 10 May 2024 11:48:27 -0400 [thread overview]
Message-ID: <87msoxk6r8.fsf@freakingpenguin.com> (raw)
In-Reply-To: <87a5kxga9x.fsf@ngraves.fr> (Nicolas Graves via's message of "Fri, 10 May 2024 13:46:02 +0200")
> One possible use would be to make `guix download` options, such as
> `--patchset=70XXX -v3`
>
> This could help with patch apply and review. We will have to also take
> care of not making guix dependent on b4, but maybe that's possible with
> lazy resolving the b4 package?
>
> WDYT?
>
From my perspective having a pretty, command-line way to download patch
sets would be a nice QoL feature to have and might make the patch review
process simpler.
On a related note I recently discovered that issues.guix.gnu.org does
have a patch-set endpoint that optionally takes a revision e.g.
issues.guix.gnu.org/issue/70XXX/patch-set/3.
--
Take it easy,
Richard Sent
Making my computer weirder one commit at a time.
next prev parent reply other threads:[~2024-05-10 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 13:35 (almost) deterministic patchsets Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2024-02-24 23:05 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2024-05-10 11:46 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2024-05-10 15:48 ` Richard Sent [this message]
2024-05-10 22:51 ` Ricardo Wurmus
2024-05-10 22:51 ` Ricardo Wurmus
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=87msoxk6r8.fsf@freakingpenguin.com \
--to=richard@freakingpenguin.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=ngraves@ngraves.fr \
--cc=zimoun.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).