From: "Bence Ferdinandy" <bence@ferdinandy.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: Re: branch description as a note?
Date: Thu, 12 Dec 2024 11:48:10 +0100 [thread overview]
Message-ID: <D69NVGIBKYO2.R5Q7TP69X6C8@ferdinandy.com> (raw)
In-Reply-To: <xmqqseqthg0h.fsf@gitster.g>
On Thu Dec 12, 2024 at 02:00, Junio C Hamano <gitster@pobox.com> wrote:
> "Bence Ferdinandy" <bence@ferdinandy.com> writes:
>
>> Not to a commit, but to a branch. I mean I know a branch is just a reference to
>> a specific commit, but in this case the mapping would be from the branch's
>> _name_ to the note object.
>
> I am not really sure if you know what you said you know above.
>
> Notes are designed to map object names to blobs (technically you can
> point at a random other objects but "notes edit" and other UI would
> only work with blobs). A branch does not have its "object name",
> because it is *not* an object.
>
> What you are saying sounds like "I know a screwdriver is not a
> chisel, but a screwdriver has a flat blade-like head, so I want to
> use it as a chisel".
Well, what I meant is that at this point, it doesn't matter to me if it
requires building a new type of nuclear powered chisel, but it would be nice if
the handle were similar to that of the screwdriver :) I.e. a user probably
doesn't care how exactly the effect is achieved, they would just want to edit
some text that is tied to the branch, not commits.
next prev parent reply other threads:[~2024-12-12 10:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 10:39 branch description as a note? Bence Ferdinandy
2024-12-11 16:11 ` Junio C Hamano
2024-12-11 17:37 ` Konstantin Ryabitsev
2024-12-11 22:11 ` Bence Ferdinandy
2024-12-12 1:39 ` Junio C Hamano
2024-12-12 2:30 ` Konstantin Ryabitsev
2024-12-11 21:57 ` Bence Ferdinandy
2024-12-12 1:00 ` Junio C Hamano
2024-12-12 10:48 ` Bence Ferdinandy [this message]
2024-12-11 17:34 ` Justin Tobler
2024-12-11 22:02 ` Bence Ferdinandy
2024-12-12 1:52 ` Junio C Hamano
2024-12-12 10:57 ` Bence Ferdinandy
2024-12-11 20:13 ` Kristoffer Haugsbakk
2024-12-11 22:07 ` Kristoffer Haugsbakk
2024-12-12 10:48 ` Oswald Buddenhagen
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=D69NVGIBKYO2.R5Q7TP69X6C8@ferdinandy.com \
--to=bence@ferdinandy.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).