unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: 44625@debbugs.gnu.org
Subject: [bug#44625] [PATCH] gnu: Add b4.
Date: Sat, 14 Nov 2020 14:36:42 +0100	[thread overview]
Message-ID: <86361cys9h.fsf@tournier.info> (raw)
In-Reply-To: <87wnyo5x7v.fsf@kyleam.com>

Hi,

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


On Sat, 14 Nov 2020 at 00:22, Kyle Meyer <kyle@kyleam.com> wrote:

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

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,
simon

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

  <https://updates.orgmode.org/>

bridging <issues.guix.gnu.org> and
<lists.gnu.org/archive/html/{{bug,help}-guix,guix-{devel,patches}}>
(or an instance of public-inbox as <yhetil.org>)
and <ci.guix.gnu.org> and <data.guix.gnu.org>,
even maybe <logs.guix.gnu.org>.

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 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:
  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=86361cys9h.fsf@tournier.info \
    --to=zimon.toutoune@gmail.com \
    --cc=44625@debbugs.gnu.org \
    --cc=kyle@kyleam.com \
    --subject='Re: [bug#44625] [PATCH] gnu: Add b4.' \
    /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

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 NNTP newsgroup(s).