Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107246 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 27937 invoked from network); 20 Sep 2019 07:10:38 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 20 Sep 2019 07:10:38 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id CA6C62D20FC for ; Thu, 19 Sep 2019 21:48:26 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Virus: No Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Thu, 19 Sep 2019 21:48:26 -0700 (PDT) Received: by mail-qk1-x72f.google.com with SMTP id 4so6004204qki.6 for ; Thu, 19 Sep 2019 21:48:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=xkSmuzXYSiqF4/SLRSyIVlS+O29BXtKotxqxWsByu4k=; b=bcUqxfsdr54fputC+gZ6lEksNK5oxV/TS/DRoiadWYQHbGnfaH3sGUMPERaqVIUNac kT8uNlP5oCIFAlLG8OeeczJbYvHQ3I4P1l5GXntVEkGhnXY6k52oC2BaZTi1ToKhY4m7 Za3UQ74dHFKu1SCC8HWEP1FTRQb5MyoNeY7xBzvC4YgW+CBJnQ0FzWxzplp2EHLljZmi PcoUlWfpHB+9xHx1JkCoJB6I6mlhikeem/5gnDvwkjNAFsseohTPB6wioyNQfhXqH9Ti h23/9CxKhkPiW1Djfjsz4rbz589eOHhtvxneVqC9kkJYsn28pX+PNnmEOjW9kctfDYCN kfpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=xkSmuzXYSiqF4/SLRSyIVlS+O29BXtKotxqxWsByu4k=; b=dufu+mz8DhzjHtlbvTq8GjH8/EuwjCtN5zKNpnrbQyCjd6mFuEq1/xuq6M402ji5UR hJFMIpUPkAy3o4AAWAMNP2E59xymWLYFv3PrnyVMty1OIBZg5648SWGjoTlYIAzCPXYm QCqQMMzvU0SziIlOWKH8mFCpHEuEt74MWUqJQGN9W/LtWo7iO+DdI1UQ0QdoCDbsNfSw MLpNMzza1eywXzr8rVPUTkpyl6AcbeK5N5DQobc2mr1OCHif2JtYW13sWFKdwI77UAGw pkZiQPZLdDEazzFO2D0amlj7B/jiU/7W2qlq7KUtzK2mVsbqyfCwMgWCVcebcwkrUXkI RTyg== X-Gm-Message-State: APjAAAX1bXfJOOE8D2Vg03SIymbbSCyL3YzXfW3hR617VmY0D4PQ3KwG 6o0ErszQzQowBLkExkVUFMPa1XInYPx4S9mwSnPOREU3IGw= X-Google-Smtp-Source: APXvYqyu8qYCtxqXeWU2NBclDA/MoNgtmSVEafJUFAV98W8iACePo+8mgnPMacIxvkeBQy2TpfG304qcRTKif9189Hw= X-Received: by 2002:a37:44e:: with SMTP id 75mr1606763qke.99.1568954905486; Thu, 19 Sep 2019 21:48:25 -0700 (PDT) MIME-Version: 1.0 Date: Fri, 20 Sep 2019 00:48:00 -0400 Message-ID: To: PHP internals Content-Type: multipart/alternative; boundary="000000000000cf6a110592f4c767" X-Envelope-From: Subject: Should changes to EXTENSIONS be with a direct master commit? From: bishop.bettini@gmail.com (Bishop Bettini) --000000000000cf6a110592f4c767 Content-Type: text/plain; charset="UTF-8" I've got the change below staged locally, but as you can see it's direct to master. Since that's an atypical workflow, and a first time for me, I wanted to check before I push. --- BEGIN git log --- commit f94d9dcc102ea5515974b3a721286a6b49840860 (HEAD -> master) Author: Bishop Bettini Date: Fri Sep 20 00:31:59 2019 -0400 [ci skip] Add phar + imap maintainer email Looks like commit c09b13cb (Add Bishop Bettini as maintainer for phar & imap, 2019-03-16) missed adding my email address. --- END git log --- Is this an appropriate case for a direct master commit? --000000000000cf6a110592f4c767--