Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119135 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 722 invoked from network); 13 Dec 2022 17:30:59 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 13 Dec 2022 17:30:59 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 5950D180556 for ; Tue, 13 Dec 2022 09:30:58 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: ** X-Spam-Status: No, score=3.0 required=5.0 tests=BAYES_20,HTML_MESSAGE, SPF_HELO_NONE,SPF_SOFTFAIL,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS24971 77.93.192.0/19 X-Spam-Virus: No X-Envelope-From: Received: from mail-mahalux.mvorisek.com (mail-mahalux.mvorisek.com [77.93.195.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 13 Dec 2022 09:30:57 -0800 (PST) Received: from 6487e53c7791 (10.228.0.209) by mail-mahalux.mvorisek.com (10.228.0.4) with Microsoft SMTP Server (TLS); Tue, 13 Dec 2022 18:30:56 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_1770876aca2489d192c4ba6462e828e9" Date: Tue, 13 Dec 2022 18:30:56 +0100 To: internals@lists.php.net Message-ID: <4c1e58ca94c3069b8704b7068254fe3926c5ad17ab62bf88bfed79de0c62bd10@mahalux.com> X-Mailer: SAP NetWeaver 7.03 Subject: Remove PHP-x.y.* git branches From: vorismi3@fjfi.cvut.cz (=?UTF-8?Q?Michael_Vo=C5=99=C3=AD=C5=A1ek_-_=C4=8CVUT_FJFI?=) --=_1770876aca2489d192c4ba6462e828e9 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8; format=flowed Hello everyone, I am the author of https://github.com/php/php-src/issues/10007 proposal and I would ask you for the green light to do so. There are two kinds of unusefull branches: a) the PHP-x-y-* branches - I would restrict the removal of branches that HEAD commit matches git tag HEAD-1 commit In theory the branches can be used somewhere, but they are pointless as git tag HEAD-1 is a 1:1 replacement. No data will/can be lost (and in theory, such branches can be restored anytime locally). b) the 10+ years old branches as mentioned in https://externals.io/message/102982 I do not expect these branches to be used anywhere. If 20 years old contribution is expected to be finished, the author should have a local git/svn copy and open regular PR for it :) Can we collectively agree? With kind regards / Mit freundlichen Grüßen / S přátelským pozdravem, Michael Voříšek --=_1770876aca2489d192c4ba6462e828e9--