[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#44625] [PATCH] gnu: Add b4.

From: zimoun
Subject: [bug#44625] [PATCH] gnu: Add b4.
Date: Sat, 14 Nov 2020 14:36:42 +0100


Thank you for the explanations, drifting from the patch. :-)

On Sat, 14 Nov 2020 at 00:22, Kyle Meyer <> wrote:

>> BTW, I think that base commit should be strongly encouraged when
>> submitting patches.  See [2] :-)
> I very much agree (and remember :>)

Yeah!  And the last remaining piece if “git-send-email”. :-)

> Hmm, or reading ahead, now I'm wondering if you mean _creates_ a
> worktree for applying the patch?  In that case, no, piem doesn't do
> that.  It's not something I've considered before.

Yes, somehow.  Generally, I create a new checked out worktree with a new
branch starting at base-commit, then I apply the patches in.  Well, my
sequence looks like:

  M-C-SPC M-w <base-commmit>
  C-x b <magit-guix-master>
  % c /path/to/wk/foo RET C-y RET foo RET
  C-x b <message-with-patch>
  | git gam foo

and I am not enough annoyed (yet!) to write some Emacs helper
functions.  However, if b4+piem could do that for me, should be
awesome. :-)

All the best,

After a discussion with Bastien and when I let my imagination goes far
away, it could be nice to something like:


bridging <> and
(or an instance of public-inbox as <>)
and <> and <>,
even maybe <>.

The email-based workflow with some fancy interfaces to be welcoming with
new contributors (smooth the learning curve).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]