Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B513E1077E for ; Tue, 9 Jul 2013 17:48:49 +0000 (UTC) Received: (qmail 13047 invoked by uid 500); 9 Jul 2013 17:48:49 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 12951 invoked by uid 500); 9 Jul 2013 17:48:49 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 12938 invoked by uid 99); 9 Jul 2013 17:48:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 17:48:48 +0000 X-ASF-Spam-Status: No, hits=-1.3 required=5.0 tests=FRT_ADOBE2,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of fil@adobe.com designates 64.18.1.208 as permitted sender) Received: from [64.18.1.208] (HELO exprod6og107.obsmtp.com) (64.18.1.208) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 17:48:43 +0000 Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob107.postini.com ([64.18.5.12]) with SMTP ID DSNKUdxM5oZfuoQUILLxfA95+b7+LnT4mqZE@postini.com; Tue, 09 Jul 2013 10:48:23 PDT Received: from inner-relay-2.corp.adobe.com (mail-321.sea.adobe.com [153.32.1.52]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r69HmKAI005892 for ; Tue, 9 Jul 2013 10:48:21 -0700 (PDT) Received: from nacas02.corp.adobe.com (nacas02.corp.adobe.com [10.8.189.100]) by inner-relay-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r69HmHw7018045 for ; Tue, 9 Jul 2013 10:48:19 -0700 (PDT) Received: from nambxv01a.corp.adobe.com ([10.8.189.95]) by nacas02.corp.adobe.com ([10.8.189.100]) with mapi; Tue, 9 Jul 2013 10:48:17 -0700 From: Filip Maj To: "dev@cordova.apache.org" Date: Tue, 9 Jul 2013 10:48:13 -0700 Subject: Re: CLI's master2 Thread-Topic: CLI's master2 Thread-Index: Ac58zH3ngF5jWxXMR2SxxVZm/RxzAQ== Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.5.130515 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Agree with Andrew, rename the branch to pre-3.0-history On 7/9/13 10:45 AM, "Carlos Santana" wrote: >I propose to kill master 2 branch, and instead use a tag "pre-3.0-history" > > >On Tue, Jul 9, 2013 at 1:22 PM, Andrew Grieve >wrote: > >> Good idea. Let's comment on which ones can be removed. >> >> >> On Tue, Jul 9, 2013 at 12:39 PM, Carlos Santana > >wrote: >> >> > Deleting some abandon branches might be a good cleanup exercise, and >>make >> > it clear to use 'master' >> > >> > - master2 >> > >> This we should keep around since it has a sane history. Let's rename it >> though. Maybe to "pre-3.0-history" >> >> > - future >> > >> This can be removed. >> >> > - lazy >> > - merges >> > - bb10RemovePrompt >> > - future-bb10 >> > - dependencies >> > >> This was merged and can be removed. >> >> > >> > >> > >> > >> > On Fri, Jul 5, 2013 at 12:16 PM, Filip Maj wrote: >> > >> > > Thanks Andrew! >> > > >> > > Ian, will do. >> > > >> > > On 7/5/13 8:14 AM, "Ian Clelland" wrote: >> > > >> > > >Doh. I *just* submitted a pull req against master2. >> > > > >> > > >Fil -- let me know if you have any problems with it, and I'll >>resubmit >> > as >> > > >necessary. >> > > > >> > > > >> > > >On Fri, Jul 5, 2013 at 8:50 AM, Andrew Grieve >> >> > > >wrote: >> > > > >> > > >> Okay, I made master look like master2, but the commit log is >> > essentially >> > > >> lost. Have not removed master2. >> > > >> >> > > >> git rm -r . >> > > >> git checkout --theirs master2 -- . >> > > >> git commit -a >> > > >> >> > > >> >> > > >> Maybe lets now go back to committing to master, and keep master2 >> > around >> > > >>for >> > > >> history's sake? >> > > >> >> > > >> >> > > >> >> > > >> On Thu, Jul 4, 2013 at 1:22 PM, Michal Mocny >> >> > > >>wrote: >> > > >> >> > > >> > (small correction, next was actually called future). >> > > >> > >> > > >> > Also, I don't see any work being done on master. >> > > >> > >> > > >> > >> > > >> > On Thu, Jul 4, 2013 at 1:18 PM, Michal Mocny >>> > >> > > >> wrote: >> > > >> > >> > > >> > > If master is in use, then I think that is a mistake. >> > > >> > > >> > > >> > > As far as I'm aware, master branch should be "dead" right? >>We >> > had a >> > > >> > > 'next' branch that was for 3.0 work which diverged from >>master >> and >> > > >>the >> > > >> > > merge back was not clean (for various reasons), hence we >> > > >>"temporarily" >> > > >> > went >> > > >> > > with a master2 until we could just "overwrite" master. Since >> that >> > > >> seems >> > > >> > to >> > > >> > > not be possible, Andrew is suggesting we go ahead with the >>not >> > clean >> > > >> > merge >> > > >> > > (history may look awkward), but do away with this ridiculous >> > > >>situation. >> > > >> > > >> > > >> > > Did I summarize that right? >> > > >> > > >> > > >> > > >> > > >> > > On Thu, Jul 4, 2013 at 1:01 PM, Brian LeRoux >> wrote: >> > > >> > > >> > > >> > >> So, what is the difference between master and master2? Right >> now, >> > > >> > >> master from what I understand is in heavy use w/ tonnes of >>bugs >> > and >> > > >> > >> fixes. >> > > >> > >> >> > > >> > >> On Thu, Jul 4, 2013 at 9:52 AM, Ian Clelland < >> > iclelland@google.com >> > > > >> > > >> > >> wrote: >> > > >> > >> > We've had that ticket open for some time now, and Braden >>has >> > > >>tried >> > > >> on >> > > >> > a >> > > >> > >> > couple of occasions to get some movement on it, but >>there's >> > been >> > > >>no >> > > >> > >> action >> > > >> > >> > so far. >> > > >> > >> > >> > > >> > >> > >> > > >> > >> > On Thu, Jul 4, 2013 at 12:34 PM, Filip Maj >> > > wrote: >> > > >> > >> > >> > > >> > >> >> If you want to give it a shot, go for it! >> > > >> > >> >> >> > > >> > >> >> Didn't we have an INFRA issue filed for them to move the >> > master >> > > >> HEAD >> > > >> > >> >> pointer to master2 and fix this for us? :P >> > > >> > >> >> >> > > >> > >> >> On 7/4/13 9:23 AM, "Andrew Grieve" >> > > wrote: >> > > >> > >> >> >> > > >> > >> >> >I feel that having master2 around is now causing us more >> harm >> > > >>than >> > > >> > >> would >> > > >> > >> >> >be >> > > >> > >> >> >done if we just merged it into master. I'd like to >>merge it >> > > >>into >> > > >> > >> master, >> > > >> > >> >> >delete master2, and move on. >> > > >> > >> >> >> > > >> > >> >> >> > > >> > >> >> > > >> > > >> > > >> > > >> > > >> > >> > > >> >> > > >> > > >> > >> > >> > -- >> > Carlos Santana >> > >> > >> > > > >--=20 >Carlos Santana >