all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Kyle Meyer <kyle@kyleam.com>, 44625@debbugs.gnu.org
Subject: [bug#44625] [PATCH] gnu: Add b4.
Date: Sat, 14 Nov 2020 03:14:26 +0100	[thread overview]
Message-ID: <86ima8d6rh.fsf@tournier.info> (raw)
In-Reply-To: <20201114003906.25111-1-kyle@kyleam.com>

Hi Kyle,

I have not tried your patch, yet.  And I have questions about tooling,
maybe it is not the right place to do so.


On Fri, 13 Nov 2020 at 19:39, Kyle Meyer <kyle@kyleam.com> wrote:

>   b4 is focused on lore.kernel.org public-inbox archives, but it's useful for
>   any public-inbox [1] instance, including yhetil.org/guix-patches :).  Here's
>   an example with a recent multi-patch thread that involves multiple versions.

Look super useful.

>     $ # in the guix repo
>     $ git config b4.attestation-policy off
>     $ git config b4.midmask https://yhetil.org/guix-patches/%s
>     $ b4 am 20201028165112.28575-1-zimon.toutoune@gmail.com
>
>   The end result is a filtered mbox with the v2 patches.  Also, because the
>   sender helpfully included the base commit, `b4 am' will use that information
>   in the instructions that it outputs.

You mean ’b4’ filters out the 2 Ludo’s messages when applying the 2
patches, right?

In this case, ’b4’ will also fetch the patches from yhetil.org, right?

If <issues.guix.gnu.org> exposes (somewhere?) the Message-ID (as we have
discussed [1]), then one user could browse, copy the Message-ID that
they is interested and paste locally as you explain above; without the
need to subscribe or use Emacs-Debbugs.  Right?


BTW, I think that base commit should be strongly encouraged when
submitting patches.  See [2] :-)

1; <https://yhetil.org/guix-devel/86sgbhz3fe.fsf@gmail.com>
2: <https://yhetil.org/guix-patches/20201012082003.19936-1-zimon.toutoune@gmail.com>


>   If the above sounds useful to you but you'd prefer to work in Emacs, you
>   might be interested in piem (<https://git.kyleam.com/piem/about/>), which
>   includes a transient (i.e magit-popup's successor) interface to b4.

I have not tried either.  Is it packaged for Guix?


Well, does b4 and piem works with worktree?

Currently, I am using Emacs and Notmuch.  I have subscribed to
guix-patches and when I try a patch, I do:

  | git gam the-branch-worktree

where ’gam’ is just ’-C ~/src/guix/wk/ am -3 --reject’.  And depending
on the thread structure, sometimes I have to go patch by patch.

Using b4+piem, then reading the message, I will do ’M-x piem-b4-am’ and
whatever the thread structure, the patches sent as “in-reply-to“ will be
applied.  Right?

(Aside messages including non inlined patches, if I read correctly the
doc.)


All the best,
simon




  reply	other threads:[~2020-11-14  2:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-14  0:39 [bug#44625] [PATCH] gnu: Add b4 Kyle Meyer
2020-11-14  2:14 ` zimoun [this message]
2020-11-14  5:22   ` Kyle Meyer
2020-11-14 13:36     ` zimoun
2020-11-15 20:18 ` bug#44625: " Christopher Baines
2020-11-15 20:53   ` [bug#44625] " Kyle Meyer

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86ima8d6rh.fsf@tournier.info \
    --to=zimon.toutoune@gmail.com \
    --cc=44625@debbugs.gnu.org \
    --cc=kyle@kyleam.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.