unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "jgart" <jgart@dismail.de>
Cc: guix-devel@gnu.org
Subject: Re: Patch Review Flow
Date: Tue, 07 Nov 2023 12:24:41 -0500	[thread overview]
Message-ID: <875y2djx2e.fsf@gmail.com> (raw)
In-Reply-To: <ed1a8fefd217dc9fccaad1ff82c97475@dismail.de> (jgart@dismail.de's message of "Sun, 05 Nov 2023 21:25:59 +0000")

Hi jgart,

"jgart" <jgart@dismail.de> writes:

> Hi Guixers,
>
> Does anyone follow this workflow for reviewing patches?
>
> git clone https://git.guix-patches.cbaines.net/guix-patches/
> git checkout issue-xxxxx
> git format-patch ...
> # then in the development checkout of Guix:
> git am ...; make; ./pre-inst-env guix build
>
> Should we document it in the manual?

There are many flows... perhaps we should illustrate them via examples
in the Guix Cookbook manual?

> Does anyone follow a workflow that is more efficient than the above?

You can use the 'b4' tool to apply a series via a message's Message-ID
that is from that series.  Or you can use Emacs-Debbugs patch buffer
(which is powered by Gnus), ensure your current directory for the main
buffer is set to your Guix checkout (e.g. 'M-x cd RET ~/src/guix'), then
apply the patches pressing the '|' to pipe it to 'git am -3' command
with it.

-- 
Thanks,
Maxim


  parent reply	other threads:[~2023-11-07 17:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-05 21:25 Patch Review Flow jgart
2023-11-06  7:51 ` Christopher Baines
2023-11-06 13:51   ` Clément Lassieur
2023-11-07  8:56   ` Efraim Flashner
2023-11-07 12:32   ` jgart
2023-11-07 12:38     ` Efraim Flashner
2023-11-07 16:29     ` jgart
2023-11-06 14:49 ` jgart
2023-11-07 17:24 ` Maxim Cournoyer [this message]
2023-11-07 20:09 ` jgart
2023-12-10 12:47   ` Tobias Alexandra Platen

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=875y2djx2e.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    /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).