From: Junio C Hamano <gitster@pobox.com>
To: Jimit Bhalavat <jimit@rams.colostate.edu>
Cc: David Huseby <dhuseby@linuxfoundation.org>, git@vger.kernel.org
Subject: Re: GPG Commit Signing Project
Date: Tue, 18 Aug 2020 13:32:18 -0700 [thread overview]
Message-ID: <xmqq5z9fy9t9.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <43C81FDC-611D-45A1-9525-24640FEB2E1A@rams.colostate.edu> (Jimit Bhalavat's message of "Tue, 18 Aug 2020 12:43:45 -0600")
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.
next prev parent reply other threads:[~2020-08-18 20:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 18:43 GPG Commit Signing Project Jimit Bhalavat
2020-08-18 20:32 ` Junio C Hamano [this message]
2020-08-19 10:19 ` brian m. carlson
-- strict thread matches above, loose matches on Subject: below --
2020-07-07 18:01 Jimit Bhalavat
2020-07-07 19:10 ` Junio C Hamano
2020-06-10 23:11 Jimit Bhalavat
2020-06-10 18:06 Jimit Bhalavat
2020-06-10 19:35 ` Junio C Hamano
2020-06-12 1:55 ` dwh
2020-06-12 2:24 ` brian m. carlson
2020-06-12 17:03 ` Junio C Hamano
2020-06-10 17:57 Jimit Bhalavat
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq5z9fy9t9.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=dhuseby@linuxfoundation.org \
--cc=git@vger.kernel.org \
--cc=jimit@rams.colostate.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).