discussion and development of piem
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: piem@inbox.kyleam.com
Subject: [RFC PATCH 00/14] am, b4-am: Add commands to extend an existing branch
Date: Wed, 29 Dec 2021 18:50:22 -0500	[thread overview]
Message-ID: <20211229235036.372313-1-kyle@kyleam.com> (raw)

Every now and then I think that it'd be nice to have commands that
extend an existing branch rather than create a new one.  But then I
end up concluding that most of the time I really do want to create a
new branch; for the other times, it's pretty easy to instead apply to
a detached head and then merge that into the target branch (e.g., with
magit-merge-into).

I had the thought again recently and decided to see how going in this
direction looked.  The result is this somewhat raw series (at the very
least, names and key bindings probably need more thought, and the
manual needs an update).  Patches 7, 12, 13, and 14 are the main
user-facing changes.

I'm still undecided about the overall direction at this point, though
I plan to at least extract and modify some patches from this series.
I have the feeling that the piem-am functionality is bound to be moved
under a transient at some point to give provide real estate for new
functionality.  That might be a good reason to take some of the prep
patches, though that shouldn't be the sole reason for adding these new
"extend existing branch" variants.

Note that, in piem's pre-1.0 release state, I am not considering
backwards compatibility as a reason to avoid these changes.

  [ 1/14] am: Give better name to default piem-am-read-worktree-function value
  [ 2/14] am: Add dedicated function for reading worktree
  [ 3/14] am: Extract git-am logic to dedicated function
  [ 4/14] am: Add function for reading piem-am's arguments
  [ 5/14] am: Add comment header for patch editing subsection
  [ 6/14] edit patch: Inject values via interactive arguments
  [ 7/14] am, b4-am: Rename piem-am to piem-am-create
  [ 8/14] am, b4-am: Rewrite -create docstrings to emphasize branch creation
  [ 9/14] piem-am-create: Move info argument to the end
  [10/14] piem-am--arguments: Make info extraction optional
  [11/14] b4: Move logic for checking arguments to a dedicated function
  [12/14] am, b4-am: Add commands that extend an existing branch
  [13/14] am: Move functionality under a dedicated transient
  [14/14] b4: Add piem-b4-am-from-mid-extend to transient

 Documentation/piem.texi |  51 +++++++------
 piem-b4.el              |  65 ++++++++++------
 piem.el                 | 159 ++++++++++++++++++++++++++--------------
 3 files changed, 174 insertions(+), 101 deletions(-)


base-commit: afa9e05e5bb42d88b0c5cf79bdcb8fbd14fdd800
-- 
2.34.0


             reply	other threads:[~2021-12-29 23:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29 23:50 Kyle Meyer [this message]
2021-12-29 23:50 ` [RFC PATCH 01/14] am: Give better name to default piem-am-read-worktree-function value Kyle Meyer
2022-02-05 17:37   ` Kyle Meyer
2021-12-29 23:50 ` [RFC PATCH 02/14] am: Add dedicated function for reading worktree Kyle Meyer
2021-12-29 23:50 ` [RFC PATCH 03/14] am: Extract git-am logic to dedicated function Kyle Meyer
2021-12-29 23:50 ` [RFC PATCH 04/14] am: Add function for reading piem-am's arguments Kyle Meyer
2021-12-29 23:50 ` [RFC PATCH 05/14] am: Add comment header for patch editing subsection Kyle Meyer
2021-12-29 23:50 ` [RFC PATCH 06/14] edit patch: Inject values via interactive arguments Kyle Meyer
2022-02-05 17:48   ` Kyle Meyer
2021-12-29 23:50 ` [RFC PATCH 07/14] am, b4-am: Rename piem-am to piem-am-create Kyle Meyer
2021-12-29 23:50 ` [RFC PATCH 08/14] am, b4-am: Rewrite -create docstrings to emphasize branch creation Kyle Meyer
2021-12-29 23:50 ` [RFC PATCH 09/14] piem-am-create: Move info argument to the end Kyle Meyer
2021-12-29 23:50 ` [RFC PATCH 10/14] piem-am--arguments: Make info extraction optional Kyle Meyer
2021-12-29 23:50 ` [RFC PATCH 11/14] b4: Move logic for checking arguments to a dedicated function Kyle Meyer
2021-12-29 23:50 ` [RFC PATCH 12/14] am, b4-am: Add commands that extend an existing branch Kyle Meyer
2021-12-29 23:50 ` [RFC PATCH 13/14] am: Move functionality under a dedicated transient Kyle Meyer
2021-12-29 23:50 ` [RFC PATCH 14/14] b4: Add piem-b4-am-from-mid-extend to transient 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://git.kyleam.com/

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

  git send-email \
    --in-reply-to=20211229235036.372313-1-kyle@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.com \
    --subject='Re: [RFC PATCH 00/14] am, b4-am: Add commands to extend an existing branch' \
    /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

Code repositories for project(s) associated with this inbox:

	https://git.kyleam.com/piem/

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