Re: [PATCH 15/18] the beginning of the signed push

From: Bert Wesarg <bert.wesarg@googlemail.com>
Date: Aug 20, 2014, 06:57 UTC
Message-ID: <CAKPyHN0Q2bCiNy0goxZ7YnmPjbU9fyjpWYmPF8gKz8T862jvAA@mail.gmail.com>
In-Reply-To: <1408485987-3590-16-git-send-email-gitster@pobox.com>

On Wed, Aug 20, 2014 at 12:06 AM, Junio C Hamano <gitster@pobox.com> wrote:

Show 10 quoted lines

> The basic flow based on this mechanism goes like this:
>
>  1. You push out your work with "git push -s".
>
>  2. The sending side learns where the remote refs are as usual,
>     together with what protocol extension the receiving end
>     supports.  If the receiving end does not advertise the protocol
>     extension "push-cert", the sending side falls back to the normal
>     push that is not signed.
>

Is this fallback silently? If so I think it would be better to abort the push, if the receiver does not support this but the user requested it.

Bert

$ 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.