git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: A note on the 5.12-rc1 tag

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 5, 2021, 23:38 UTC
Message-ID
<xmqqmtvh893r.fsf@gitster.c.googlers.com>
In-Reply-To
<YEK5d+8TSqS/rdMu@localhost>
Josh Triplett <josh@joshtriplett.org> writes:
Show 11 quoted lines
>> It is trivial for you to fetch the refs/notes/do-not--checkout notes
>> tree from me and merge it into your refs/notes/do-not--checkout
>> notes tree, I would think; "git notes merge" may have room for
>> improvement, but essentially it would just want a union of two
>> sets, no?
>
> My primary concern about notes is that they require manual
> action/configuration in order to share. I was looking for a solution
> that would automatically protect anyone who pulled from linux.git
> (directly or indirectly), without them having to specifically take a
> separate step to sync this information.

If "without any configuration" is a hard requirement, then by definition you'd need to live with what you get from "git clone" and "git pull" alone, so be it the notes or any other mechanism, there currently is nothing that lets you do the "skip this part while bisection".

Previous: Josh Triplett
Message 5 of 5 in “Re: A note on the 5.12-rc1 tag”
  1. Josh TriplettMar 4, 2021
  2. Christian CouderMar 5, 2021
  3. Junio C HamanoMar 5, 2021
  4. Josh TriplettMar 5, 2021
  5. Junio C HamanoMar 5, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.