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

Re: GPG Commit Signing Project

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 18, 2020, 20:32 UTC
Message-ID
<xmqq5z9fy9t9.fsf@gitster.c.googlers.com>
In-Reply-To
<43C81FDC-611D-45A1-9525-24640FEB2E1A@rams.colostate.edu>
Jimit Bhalavat <jimit@rams.colostate.edu> writes:
> Hello Junio,

Sorry, I read the message twice but I am not sure what you expect out of me. We usually do not evaluate a proposal only from its "design document" in the sense that we won't say neither "such a proposal is great" or "we won't accept such a proposal" until we actually see patches. It is a good idea to have a written design as it may help reviewers when they review patch submission.

> 	5. All of these changes will make sure that we maintain
> 	backwards compatibility. We are aiming to deprecate things a
> 	little but old options will not stop working. We will
> 	preserve existing behavior.

That is always a requirement by our project so it goes without saying ;-) but it is good to see the promise written down.

Previous: Jimit BhalavatNext: brian m. carlson
Message 2 of 3 in “GPG Commit Signing Project”
  1. Jimit BhalavatAug 18, 2020
  2. Junio C HamanoAug 18, 2020
  3. brian m. carlsonAug 19, 2020

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.