Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101195 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87897 invoked from network); 29 Nov 2017 02:22:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Nov 2017 02:22:07 -0000 Authentication-Results: pb1.pair.com smtp.mail=php@golemon.com; spf=softfail; sender-id=softfail Authentication-Results: pb1.pair.com header.from=php@golemon.com; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.216.169 as permitted sender) X-PHP-List-Original-Sender: php@golemon.com X-Host-Fingerprint: 209.85.216.169 mail-qt0-f169.google.com Received: from [209.85.216.169] ([209.85.216.169:34927] helo=mail-qt0-f169.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EF/43-57104-EC91E1A5 for ; Tue, 28 Nov 2017 21:22:06 -0500 Received: by mail-qt0-f169.google.com with SMTP id u10so2573215qtg.2 for ; Tue, 28 Nov 2017 18:22:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=golemon-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=3KSrwO0p75qbPIBJGf8cBdntX4Gq9IjKOmdr/L2s50U=; b=K1/UlZmjE69B2DF20tTYFZzmvsxZ4JMI/Am6TL3bPYPm/8A+W5rZeYwIrsBNJhpXr/ CYLfpuWJcITbzWRCGhimJg8/TQMdPIAKKrULNToQ+r5WV788vUmyTLmK/EuQe0uulOBZ ugPffyrA8NWu6OsZGWj9Xern+Y5t3cWfwWmC7cL55Cs2d5gDiv8dH8CZzeyBHJcGmlOf I517tcQapXvU5IMX4ZDN4Uhf7a3Q4omLhFUKCeKieONMOBBpRO/vIYg3syrgFF1TTIZy oQTIEh/mfJbQ8iaWzH+2elcm+5sXgHBlG8kOEINS7fJAmRfl5dyxgdfOa17nyipDKAoK JsGA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=3KSrwO0p75qbPIBJGf8cBdntX4Gq9IjKOmdr/L2s50U=; b=AfYuHYEpR7/eT1DN+kea0/ezHlw+P3e4tjCyyZLKKqV9UuynGpKKnNZsnlIuur+rYJ /Tldoo+BRkdgembTKxKXKOVLV0KKttccn6dCgVI8LCFl/uLiwnfbAouiw1FO/Zy27A7R 0zu54tLSQYXM+yv8svyEJ655ooJt4AxqLT4jHP/Sh1dLMPEbtW57F2IcX34TW/rLxQxF NKfCjfhF4cEMFSXZH+UXurnMBqNRLybGpdkWOSqjrNUpwQLzz4WSohHFdJ0EnFDBLNSK WF8Tvl2wwk586B52w0d+efrGgJuBp37BBRaQs4sNVJLAR3gFIXoC2Amt17j3Y4VQtDS5 yCOA== X-Gm-Message-State: AJaThX4X+tL6mUIxfb+trY1xHfMzNbzG/GChgDqd2A1CV+WnCk58xdBx ACkY6QhKadc4ayxmsv6G2tMzk2FdZErs3nnCpQGjiQ== X-Google-Smtp-Source: AGs4zMaL3dC1OzBrYNmgDzvO6PM5zC3SEEZctQ874sCSaKHB6hCqr59xrCJgWYpeh+jhTULoajn00NQIzyhQOONkDeQ= X-Received: by 10.200.63.161 with SMTP id d30mr2223249qtk.311.1511922124045; Tue, 28 Nov 2017 18:22:04 -0800 (PST) MIME-Version: 1.0 Sender: php@golemon.com Received: by 10.12.158.145 with HTTP; Tue, 28 Nov 2017 18:22:03 -0800 (PST) X-Originating-IP: [71.251.16.204] In-Reply-To: <8888326c-553e-3d57-1077-8f23a66d371c@gmail.com> References: <8888326c-553e-3d57-1077-8f23a66d371c@gmail.com> Date: Tue, 28 Nov 2017 21:22:03 -0500 X-Google-Sender-Auth: Sb1ylQZXdAw2uHBDSMvVuGXrG50 Message-ID: To: Stanislav Malyshev Cc: Niklas Keller , PHP Internals , Joe Watkins , Remi Collet , Anatol Belski Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] Public Tags of Releases From: pollita@php.net (Sara Golemon) On Tue, Nov 28, 2017 at 7:30 PM, Stanislav Malyshev wrote: >> If there's a mistake that needs to be fixed and that's detected within >> these two days, a re-tag needs to happen. If the old tag is deleted and a >> new modified tag is published, all cloned Git repositories that already >> received the old tag will keep the old tag and never receive the new tag >> unless the old tag is manually removed first. That's problematic. > > That's not how git is supposed to work? If you syncronize the repo you > should get the new tag. If you cloned repo once and never update then of > course you don't get new tag, but you also don't get the fix... > Erm, actually no, it's not how git is supposed to work. If you have an up to date checkout of php-src/master right now, it contains the php-7.2.0 tag. If Remi adds more commits (to fix something) and moves that tag to the new head of the PHP-7.2.0 branch and pushes it, then anyone who HADN'T YET synced php-src/master since this morning will get the new tag fine, but you never will (not with a normal `git pull`, anyway). This is because git will not change tags unless you explicitly tell it it's okay to. Moving git tags after they've been pushed to a remote (shared) repo is as much a sin as force pushing. It shouldn't be done. -Sara