Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58716 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 32901 invoked from network); 7 Mar 2012 06:04:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Mar 2012 06:04:21 -0000 Authentication-Results: pb1.pair.com header.from=drak@zikula.org; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=drak@zikula.org; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zikula.org designates 209.85.216.170 as permitted sender) X-PHP-List-Original-Sender: drak@zikula.org X-Host-Fingerprint: 209.85.216.170 mail-qy0-f170.google.com Received: from [209.85.216.170] ([209.85.216.170:45228] helo=mail-qy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C5/59-15021-46AF65F4 for ; Wed, 07 Mar 2012 01:04:21 -0500 Received: by qcmt36 with SMTP id t36so3466083qcm.29 for ; Tue, 06 Mar 2012 22:04:18 -0800 (PST) Received: by 10.229.137.85 with SMTP id v21mr58570qct.70.1331100258185; Tue, 06 Mar 2012 22:04:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.171.97 with HTTP; Tue, 6 Mar 2012 22:03:58 -0800 (PST) In-Reply-To: <4F53DF00.6070303@gmx.net> References: <4F5336B2.3040200@kukulich.cz> <4F53DF00.6070303@gmx.net> Date: Wed, 7 Mar 2012 11:48:58 +0545 Message-ID: To: internals@lists.php.net Content-Type: multipart/alternative; boundary=00235452e9600cb0e104baa0ee2a X-Gm-Message-State: ALoCoQnTkjVJdIuIYBsYajRjxq6Yt6gaJ/mLZNzgVGOzz+DQVLHfBBYrngb15TCP5dYZAk7ih/Lk Subject: Re: [PHP-DEV] Re: Git Migration: Status Update From: drak@zikula.org (Drak) --00235452e9600cb0e104baa0ee2a Content-Type: text/plain; charset=UTF-8 On 5 March 2012 03:15, David Soria Parra wrote: > No. We will always need to be able to delete branches created, or tags > (we had situations were we needed to retag, for example). That in > itself can be used to do a forced push: > [snip] > I am also not a strong believer trying to forbid as much as possible. > If you have an SVN account you are trusted enough to not just delete > something that is used. Also thanks to the decentralized model of git > we all have backups, so we can just recreate it. Additionally, if someone force pushes a branch overwriting work it can always be recovered by a sysadmin from the reflog on the remote server. It's not a problem. However I stress, that something is pretty wrong if people are force pushing branches to the main repo and I'd personally be slapping wrists if I saw it for any project I oversee. Forcing pushes to one's own topic branches in one's own fork can be acceptable providing upstream maintainers know before merging (for example squashing some work after peer review), but not to the central repo without some exceptional reason - it could cause chaos otherwise. Regards, Drak --00235452e9600cb0e104baa0ee2a--