From: Taylor Blau <me@ttaylorr.com>
To: Bence Ferdinandy <bence@ferdinandy.com>
Cc: git@vger.kernel.org,
"Kristoffer Haugsbakk" <code@khaugsbakk.name>,
"Đoàn Trần Công Danh" <congdanhqx@gmail.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Junio C Hamano" <gitster@pobox.com>,
"SZEDER Gábor" <szeder.dev@gmail.com>,
"Teng Long" <dyroneteng@gmail.com>
Subject: Re: [RFC PATCH] notes: add prepend command
Date: Wed, 23 Oct 2024 16:20:20 -0400 [thread overview]
Message-ID: <ZxlahJygsRFcxDev@nand.local> (raw)
In-Reply-To: <20241023201430.986389-1-bence@ferdinandy.com>
On Wed, Oct 23, 2024 at 10:14:24PM +0200, Bence Ferdinandy wrote:
> When a note is detailing commit history, it makes sense to keep the
> latest change on top, but unlike adding things at the bottom with
> "git notes append" this can only be done manually. Add a
>
> git notes prepend
>
> command, which works exactly like the append command, except that it
> inserts the text before the current contents of the note instead of
> after.
Hmmm. I am not sure that I see the widespread need for such a tool. If
this is specific to your use-case, I think a custom script and
`$GIT_EDITOR` would do the trick.
Thanks,
Taylor
next prev parent reply other threads:[~2024-10-23 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 20:14 [RFC PATCH] notes: add prepend command Bence Ferdinandy
2024-10-23 20:20 ` Taylor Blau [this message]
2024-10-23 20:32 ` Bence Ferdinandy
2024-10-24 11:19 ` Đoàn Trần Công Danh
2024-10-26 22:34 ` Bence Ferdinandy
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=ZxlahJygsRFcxDev@nand.local \
--to=me@ttaylorr.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=bence@ferdinandy.com \
--cc=code@khaugsbakk.name \
--cc=congdanhqx@gmail.com \
--cc=dyroneteng@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=szeder.dev@gmail.com \
/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).