discussion and development of piem
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: piem@inbox.kyleam.com
Cc: zimoun <zimon.toutoune@gmail.com>
Subject: [PATCH 0/6] Support applying patches in a new worktree
Date: Sun, 15 Nov 2020 01:15:12 -0500	[thread overview]
Message-ID: <20201115061518.22191-1-kyle@kyleam.com> (raw)

This series is prompted by simon's patch workflow described at

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

With patch 4, something like that should be possible with both piem-am
and piem-b4-am-from-mid.  When the new piem-am-create-worktree option
is set to a non-nil value, the caller will be prompted for a directory
where the new worktree should be created.

Patch 5 makes it possible to trigger this in a one-off fashion with a
prefix argument because, while I don't want this behavior most of the
time, I could see myself using it every now and then.

  [1/6] piem-am: Rephrase CODEREPO description
  [2/6] piem-am: Store "empty string" branch check
  [3/6] am: Support creating a new worktree
  [4/6] am: Add option to configure how worktree is read
  [5/6] am: Allow flipping worktree creation with prefix argument
  [6/6] manual: Document worktree-related options

 piem-b4.el | 15 ++++++++---
 piem.el    | 77 ++++++++++++++++++++++++++++++++++++++++++------------
 piem.texi  | 15 ++++++++++-
 3 files changed, 85 insertions(+), 22 deletions(-)

base-commit: b54ad663fe22811dde804721d4db528ea18a433c

             reply	other threads:[~2020-11-15  6:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-15  6:15 Kyle Meyer [this message]
2020-11-15  6:15 ` [PATCH 1/6] piem-am: Rephrase CODEREPO description Kyle Meyer
2020-11-15  6:15 ` [PATCH 2/6] piem-am: Store "empty string" branch check Kyle Meyer
2020-11-15  6:15 ` [PATCH 3/6] am: Support creating a new worktree Kyle Meyer
2020-11-15  6:15 ` [PATCH 4/6] am: Add option to configure how worktree is read Kyle Meyer
2020-11-15  6:15 ` [PATCH 5/6] am: Allow flipping worktree creation with prefix argument Kyle Meyer
2020-11-15  6:15 ` [PATCH 6/6] manual: Document worktree-related options Kyle Meyer
2020-11-15 13:31 ` [PATCH 0/6] Support applying patches in a new worktree zimoun
2020-11-15 19:26   ` Kyle Meyer
2020-11-15 22:32     ` Kyle Meyer
2020-11-15 23:47       ` zimoun

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: https://git.kyleam.com/

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

  git send-email \
    --in-reply-to=20201115061518.22191-1-kyle@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.com \
    --cc=zimon.toutoune@gmail.com \


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