From: Junio C Hamano <gitster@pobox.com>
To: "Bence Ferdinandy" <bence@ferdinandy.com>
Cc: <git@vger.kernel.org>
Subject: Re: branch description as a note?
Date: Thu, 12 Dec 2024 10:00:30 +0900 [thread overview]
Message-ID: <xmqqseqthg0h.fsf@gitster.g> (raw)
In-Reply-To: <D697HA5ZDN2K.1I643FREX8WKC@ferdinandy.com> (Bence Ferdinandy's message of "Wed, 11 Dec 2024 22:57:22 +0100")
"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".
next prev parent reply other threads:[~2024-12-12 1:00 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 [this message]
2024-12-12 10:48 ` Bence Ferdinandy
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=xmqqseqthg0h.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=bence@ferdinandy.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.