Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113900
To: internals@lists.php.net
References: <CAF+90c9A6zG-nYzc3NNtWGjN7y5FmwqnYzjq6GSFC5NtRsOT0w@mail.gmail.com>
 <CAN2symg2SueEONzMRndsWEhj6anXmeAQwKg+HzKh-o61bcP0Qg@mail.gmail.com>
 <CAESVnVoPEitSCzmrAR2pRY4zUp4WEBc3a1b3q4H_uh1q8ebVWw@mail.gmail.com>
 <CAEYWF=71sahVwiaPEAYMCfLd+fgZ5FA24bS-LCtzxNW==9H=xg@mail.gmail.com>
Message-ID: <81874e32-ab95-8b27-ef71-7222b4ea47f6@fischer.name>
Date: Thu, 1 Apr 2021 12:01:56 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
 Gecko/20100101 Thunderbird/78.8.0
MIME-Version: 1.0
In-Reply-To: <CAEYWF=71sahVwiaPEAYMCfLd+fgZ5FA24bS-LCtzxNW==9H=xg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Spam_score: -2.9
X-Spam_score_int: -28
X-Spam_bar: --
X-Spam_report: Spam detection software, running on the system "scanner01.home", has
 identified this incoming email as possible spam.  The original message
 has been attached to this so you can view it (if it isn't spam) or label
 similar future email.  If you have any questions, see
 the administrator of that system for details.
 
 Content preview:  Hi Bishop, On 01.04.21 06:54, Bishop Bettini wrote: > I've
    documented why we need signing, and how to set it up: > > https://wiki.php.net/vcs/commit-signing
    > > Feedback welcomed! I'm not even the target audience in terms of php-src
    access, but rarely have I seen such a good tutorial approach on this (though
    have not tested it). [...] 
 
 Content analysis details:   (-2.9 points, 5.0 required)
 
  pts rule name              description
 ---- ---------------------- --------------------------------------------------
  0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was blocked.
                             See
                             http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
                              for more information.
                             [URIs: php.net]
 -1.0 ALL_TRUSTED            Passed through trusted hosts only via SMTP
 -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                             [score: 0.0000]
 -0.0 NICE_REPLY_A           Looks like a legit reply (A)
X-CMAE-Envelope: MS4wfBvxinRHTSX7D4J8iJHE44EazKPylqNfEljbf6A5xuTImhRM4WtDpDYbsQVexhEB+R0xIK44FTDrhAxIDp6gx1b81iUi4m7wCvXiFNvfZ9Hgb8pnlBsN
 y0M7E1+79qR4n+JT/y8VC4lZkMaNns9fI9Ol9T+kprs4IVH0nChbsrKj
Subject: Re: [PHP-DEV] Changes to Git commit workflow
From: markus@fischer.name (Markus Fischer)

Hi Bishop,

On 01.04.21 06:54, Bishop Bettini wrote:
> I've documented why we need signing, and how to set it up:
> 
> https://wiki.php.net/vcs/commit-signing
> 
> Feedback welcomed!

I'm not even the target audience in terms of php-src access, but rarely 
have I seen such a good tutorial approach on this (though have not 
tested it).

Just wanted to mention this, really great. It mentions it's based on 
internal LifeOmic docs, so kudos to them too I guess :)

- Markus