Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58736 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 82208 invoked from network); 7 Mar 2012 12:24:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Mar 2012 12:24:24 -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:49832] helo=mail-qy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 75/20-15180-773575F4 for ; Wed, 07 Mar 2012 07:24:23 -0500 Received: by qcmt36 with SMTP id t36so3681429qcm.29 for ; Wed, 07 Mar 2012 04:24:20 -0800 (PST) Received: by 10.229.77.17 with SMTP id e17mr252961qck.10.1331123060264; Wed, 07 Mar 2012 04:24:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.171.97 with HTTP; Wed, 7 Mar 2012 04:24:00 -0800 (PST) In-Reply-To: References: <4F5336B2.3040200@kukulich.cz> <4F53DF00.6070303@gmx.net> Date: Wed, 7 Mar 2012 18:09:00 +0545 Message-ID: To: Kiall Mac Innes Cc: internals@lists.php.net Content-Type: multipart/alternative; boundary=002354471a4028d17104baa63d90 X-Gm-Message-State: ALoCoQmByGl5fDUynaxCm8XCT5fq8QceFANLvYqe+XSg/EhQ+hvpSVcksgat/OMYp+ea9lTnRV8K Subject: Re: [PHP-DEV] Re: Git Migration: Status Update From: drak@zikula.org (Drak) --002354471a4028d17104baa63d90 Content-Type: text/plain; charset=UTF-8 On 7 March 2012 11:54, Kiall Mac Innes wrote: > On Wed, Mar 7, 2012 at 6:03 AM, Drak wrote: > >> [snip] >> 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. >> > > Gerrit has an interesting take on this, you are free to do whatever you > like on refs/heads/dev/${username}/* - including force push etc. > > Maybe something like this could be useful? > I understand, but it's totally unnecessary. Features and fixes are done on a local branch and published for review in your own local fork upstream. When you are ready you make a pull request and someone can merge in your code - or if you have write access to the central repo simple merge and push to the central branch for that feature. There is no need for complexity in the central repository. It's easy, it will just take time for contributors to find their feet if they are not used to git. Regards. Drak --002354471a4028d17104baa63d90--