unofficial mirror of 
 help / color / mirror / code / Atom feed
From: zimoun <>
To: Kyle Meyer <>
Subject: [bug#44625] [PATCH] gnu: Add b4.
Date: Sat, 14 Nov 2020 14:36:42 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


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	other threads:[~2020-11-14 14:27 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
2020-11-14  5:22   ` Kyle Meyer
2020-11-14 13:36     ` zimoun [this message]
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:

  List information:

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

  git send-email \ \ \ \ \

* 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

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).