Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58589 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 66069 invoked from network); 4 Mar 2012 21:32:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Mar 2012 21:32:16 -0000 Authentication-Results: pb1.pair.com header.from=dsoria@gmx.net; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=dsoria@gmx.net; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmx.net designates 213.165.64.22 as permitted sender) X-PHP-List-Original-Sender: dsoria@gmx.net X-Host-Fingerprint: 213.165.64.22 mailout-de.gmx.net Received: from [213.165.64.22] ([213.165.64.22:52309] helo=mailout-de.gmx.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2B/12-48673-E5FD35F4 for ; Sun, 04 Mar 2012 16:32:15 -0500 Received: (qmail invoked by alias); 04 Mar 2012 21:32:11 -0000 Received: from p4FE3BD59.dip.t-dialin.net (EHLO [192.168.23.101]) [79.227.189.89] by mail.gmx.net (mp020) with SMTP; 04 Mar 2012 22:32:11 +0100 X-Authenticated: #235172 X-Provags-ID: V01U2FsdGVkX1/G1GwCNufG5IMTi0rhi4oINMDewCmDsndMp9wdCS j7RkEV1bl1GSNy Message-ID: <4F53DF00.6070303@gmx.net> Date: Sun, 04 Mar 2012 22:30:40 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20120131 Thunderbird/10.0 MIME-Version: 1.0 To: Jaroslav Hanslik CC: internals@lists.php.net, David Soria Parra References: <4F5336B2.3040200@kukulich.cz> In-Reply-To: <4F5336B2.3040200@kukulich.cz> X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Re: Git Migration: Status Update From: dsoria@gmx.net (David Soria Parra) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/04/2012 10:32 AM, Jaroslav Hanslik wrote: >> >> (3) Karma system fixes. Already done by me. People who have >> access to the root of a repository are able to do forced pushes. >> > > > Do you think it's good idea not to forbid forced pushes at all? 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: git push :master && git push mynewmaster:master Will be equal to git push +mynewmaster:master equal to git push --force mynewmaster:master 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. David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPU98AAAoJEAT0aMuPE7Z1SM8P/1eN+edqsqoMPukCZfeeWbFm DM4wRS1UYyc4WZ2LrUi/6+hadgEk4QZLwkLiZPw+CuYwlGtkRhIoPWskV3HK4xT9 HqdMeHxTxEAjsq0dnb37hklSGc2LlTFRnUhCHkrZdGb4OZEjOXeQBVa8ud/32Exa Cjxcyrmrzdxzu65W1P203zjAwo4jCR24PgWw4qhAqqI4UNYuHhgmIvptOo0MMvZV bkZ2GzKDsZladGG+mVwHdxZNwPOU9CxFnWG36wX7tl11uX80M+4WMTTJ43T1kpif ZhqbUrUWwitaZfdLBE9apKpwzO09cQdEsY7hgezZNntyH4PmHV+NCvCgz+BBywzM ivxNSjvTj8Kt3p4Y63WXOlfdrhTG/65hoZQTMn2Mv3qSIx3lVIqnUc/UFk5WBEI/ qOBARLGBtqy1ytMTdLLAcYN3cqFKS+zV0ucYIrBClr1LeIuAkIjfXNZ55CILmGy8 KEwJn6gC495jzV3LK7dw9S0mUiVvraG3IeBsNcJr8OELPZFC/U5IZHO0o1bafXWQ I/iqAA2tPeHQ289XyyHRSqL+qQHfDwP75gB0uUcu43lSieu0bNwkCI7IotHtC5vi dePV4pzyj+Yjyicx4NcrurWW5BeLafe8l1wvzUNS7SmrtUr3ZMJkj6qIVbVq6hq5 GvGw6+527FSIwn0TUGC2 =+P5T -----END PGP SIGNATURE-----