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

Re: [Outreachy PATCH] doc: clarify promisor remote fetch ordering

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 26, 2026, 05:18 UTC
Message-ID
<xmqqy0blujid.fsf@gitster.g>
In-Reply-To
<CA+ew3Ju1N0bCFkTzrop5+ckNCrgGWRzMcrLHu7DAYufzw7Gncg@mail.gmail.com>
Wasswa Edson <edsonwasswa54@gmail.com> writes:
Show 6 quoted lines
> ... the implementation
> already has safeguards that prevent arbitrary injection
> Then about the Git server my say is a No, coz a server cannot
> arbitrarily inject a brand-new, untrusted promisor remote onto a
> client by default. The client must explicitly configure acceptance
> policies before any server-advertised remote will be accepted.

An explanation like the above must be in your proposed log message so that the next person who looks at your patch do not have to ask the same question.

Also, we frown upon top-posting on this list.
Thanks.
Previous: Wasswa Edson
Message 4 of 4 in “doc: clarify promisor remote fetch ordering”
  1. doc: clarify promisor remote fetch orderingWasswa Edson, Oct 22, 2026
  2. Junio C HamanoOct 22, 2026
  3. Wasswa EdsonOct 25, 2026
  4. Junio C HamanoOct 26, 2026

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.