From: Junio C Hamano <gitster@pobox.com>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: sideshowbarker <mike@w3.org>, git@vger.kernel.org
Subject: Re: Problem: git Notes not discoverable (+proposed solutions)
Date: Wed, 04 Sep 2024 07:54:34 -0700 [thread overview]
Message-ID: <xmqqbk13eafp.fsf@gitster.g> (raw)
In-Reply-To: <20240904071338.GW26466@kitsune.suse.cz> ("Michal Suchánek"'s message of "Wed, 4 Sep 2024 09:13:38 +0200")
Michal Suchánek <msuchanek@suse.de> writes:
> On Tue, Sep 03, 2024 at 02:34:02PM -0700, Junio C Hamano wrote:
>
> The notes could be also used to annotate existing upstream history
> without altering it.
>
> However, the problems with notes worflows make it impractical.
Indeed. As a mechanism for the only publisher to publish auxiliary
pieces of information to cloners, notes is a very useful mechanism,
but for such a use case to be effective, the project participants
must understand when they are supposed to use the notes read-only.
next prev parent reply other threads:[~2024-09-04 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 5:20 Problem: git Notes not discoverable (+proposed solutions) sideshowbarker
2024-09-03 1:06 ` Sean Allred
2024-09-04 20:03 ` Jacob Keller
2024-09-03 21:34 ` Junio C Hamano
2024-09-04 7:13 ` Michal Suchánek
2024-09-04 14:54 ` Junio C Hamano [this message]
2024-09-04 7:24 ` Kristoffer Haugsbakk
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=xmqqbk13eafp.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mike@w3.org \
--cc=msuchanek@suse.de \
/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.