From: Taylor Blau <me@ttaylorr.com>
To: Samuel Adekunle Abraham via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
Patrick Steinhardt <ps@pks.im>,
Phillip Wood <phillip.wood@dunelm.org.uk>,
Junio C Hamano <gitster@pobox.com>,
Samuel Adekunle Abraham <abrahamadekunle50@gmail.com>
Subject: Re: [PATCH v3] notes: teach the -e option to edit messages in editor
Date: Mon, 21 Oct 2024 12:52:59 -0400 [thread overview]
Message-ID: <ZxaG67wuvjOXc5kr@nand.local> (raw)
In-Reply-To: <pull.1817.v3.git.1729521495497.gitgitgadget@gmail.com>
On Mon, Oct 21, 2024 at 02:38:15PM +0000, Samuel Adekunle Abraham via GitGitGadget wrote:
> From: Abraham Samuel Adekunle <abrahamadekunle50@gmail.com>
>
> Notes can be added to a commit using:
> - "-m" to provide a message on the command line.
> - -C to copy a note from a blob object.
> - -F to read the note from a file.
> When these options are used, Git does not open an editor,
> it simply takes the content provided via these options and
> attaches it to the commit as a note.
>
> Improve flexibility to fine-tune the note before finalizing it
> by allowing the messages to be prefilled in the editor and edited
> after the messages have been provided through -[mF].
>
> Signed-off-by: Abraham Samuel Adekunle <abrahamadekunle50@gmail.com>
Nicely described, this commit message is looking good. Let's take a look
at the patch below...
> diff --git a/t/t3301-notes.sh b/t/t3301-notes.sh
> index 99137fb2357..2827f592c66 100755
> --- a/t/t3301-notes.sh
> +++ b/t/t3301-notes.sh
> @@ -1567,4 +1567,75 @@ test_expect_success 'empty notes do not invoke the editor' '
> git notes remove HEAD
> '
>
> +test_expect_success 'git notes add with -m/-F invokes editor with -e' '
> + test_commit 19th &&
> + MSG="Edited notes message" git notes add -m "Initial notes message" -e &&
> + echo "Edited notes message" >expect &&
Very nice use of the fake_editor script here.
It is a little cumbersome to repeat the same message in MSG= and when
populating the 'expect' file. Perhaps instead this could be written as:
echo "edited notes message" >expect &&
MSG="$(cat expect)" git notes -add -m "initial" -e
> + git notes show >actual &&
> + test_cmp expect actual &&
> + git notes remove HEAD &&
> +
> + # Add a note using -F and edit it
> + echo "Note from file" >note_file &&
> + MSG="Edited note from file" git notes add -F note_file -e &&
> + echo "Edited note from file" >expect &&
Same "note" here. ;-).
> + git notes show >actual &&
> + test_cmp expect actual
> +'
> +
> +test_expect_success 'git notes append with -m/-F invokes the editor with -e' '
> + test_commit 20th &&
> + git notes add -m "Initial note message" &&
> + MSG="Appended edited note message" git notes append -m "New appended note" -e &&
It's fine to use shorter values for -m and $MSG here. I think "appended"
and "edited" would be fine for each, respectively.
Besides applying those suggestions throughout the patch's new tests
(including the ones that I didn't explicitly comment on here), I think
that this should be looking good after another round. Thanks for working
on it.
Thanks,
Taylor
next prev parent reply other threads:[~2024-10-21 16:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-19 0:14 [PATCH] notes: teach the -e option to edit messages in editor Samuel Adekunle Abraham via GitGitGadget
2024-10-19 0:38 ` brian m. carlson
2024-10-19 11:03 ` Kristoffer Haugsbakk
2024-10-19 11:24 ` Samuel Abraham
2024-10-19 10:28 ` Kristoffer Haugsbakk
2024-10-19 11:19 ` Samuel Abraham
2024-10-19 11:36 ` Kristoffer Haugsbakk
2024-10-19 11:58 ` Samuel Abraham
2024-10-20 0:03 ` [PATCH v2] " Samuel Adekunle Abraham via GitGitGadget
2024-10-21 11:58 ` Patrick Steinhardt
2024-10-21 12:37 ` Samuel Abraham
2024-10-21 18:22 ` Eric Sunshine
2024-10-21 14:38 ` [PATCH v3] " Samuel Adekunle Abraham via GitGitGadget
2024-10-21 16:52 ` Taylor Blau [this message]
2024-10-21 17:12 ` Samuel Abraham
2024-10-21 18:28 ` Eric Sunshine
2024-10-21 19:52 ` Taylor Blau
2024-10-21 18:12 ` [PATCH v4] " Samuel Adekunle Abraham via GitGitGadget
2024-10-21 19:53 ` Taylor Blau
2024-10-21 21:44 ` Samuel Abraham
2024-10-23 6:14 ` Patrick Steinhardt
2024-10-23 16:51 ` Samuel Abraham
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZxaG67wuvjOXc5kr@nand.local \
--to=me@ttaylorr.com \
--cc=abrahamadekunle50@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=ps@pks.im \
--cc=sandals@crustytoothpaste.net \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).