Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: pass (nike.apache.org: domain of omuppi1@gmail.com designates
 209.85.212.51 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACK5iZcwRP41mjL8--1=zG7LcmXELeaX-OGXPi1JdDLQ0tHt5A@mail.gmail.com>
References: 
 <CACK5iZc=iiVF4eRmZeZsUY1=UYhrn+DWi6Md2cxtdapZVO7QoA@mail.gmail.com>
 <CD6BE86E.4F5E1%aharui@adobe.com>
 <CACK5iZf5Mupmg5cjYznxJk9au0m=P-kLaMjiBm6OvppJvLDwUA@mail.gmail.com>
 <CACK5iZcZ+9A3v9Qu4fjfnswMdM6Teb_tCX49TFXDjXZJ36O+=Q@mail.gmail.com>
 <CACK5iZdZsZdoCycB6wxPr5Bc1AjOG4vM5EKVCYSuY6upK4BwAw@mail.gmail.com>
 <815B2C51F4E14B5B8D1547593ADBE1B6@ixsoftware.nl>
 <CACK5iZcwRP41mjL8--1=zG7LcmXELeaX-OGXPi1JdDLQ0tHt5A@mail.gmail.com>
From: OmPrakash Muppirala <omuppi1@gmail.com>
Date: Mon, 18 Mar 2013 16:55:41 -0700
Message-ID: 
 <CACK5iZd+uYcp_ECn173YM7T5BL=vz1sB6L2ha=3SVX6V879haQ@mail.gmail.com>
Subject: Re: [LAZY] Asking Infra to make all git repos read-write.
To: dev@flex.apache.org
Content-Type: multipart/alternative; boundary=bcaec54eee80bac49004d83bbbc2

--bcaec54eee80bac49004d83bbbc2
Content-Type: text/plain; charset=ISO-8859-1

Fred and Justin, can you please let us know if we are good to go?

Thanks,
Om

On Mon, Mar 18, 2013 at 1:31 PM, OmPrakash Muppirala <omuppi1@gmail.com>wrote:

> Thanks Erik.
>
>  I think I will wait for at least Fred and Justin to give their final OKs
> - given that they have been actively working on this task.
>
> (Of course, everyone is free to give their inputs at anytime)
>
> Om
>
>
> On Mon, Mar 18, 2013 at 1:13 PM, Erik de Bruin <erik@ixsoftware.nl> wrote:
>
>> Om,
>>
>> I gave the OK in another thread (enthusiastically). As this is a LAZY
>> vote, I thought I'd be just that, as that implies consent :-)
>>
>> But here you go: +1 (binding)
>>
>> EdB
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl (http://www.ixsoftware.nl)
>>
>>
>>
>> On Monday, March 18, 2013 at 19:27, Om wrote:
>>
>> > I will ask again:
>> >
>> > Any objections to making all git repos read/write? Alex is the only
>> person
>> > who has said yes so far.
>> >
>> > Other than these anything else we need to go to Infra for?:
>> >
>> > 1. Migrate the External project to git
>> > 2. Change commit email subject format.
>> >
>> > We can decided on the whiteboard git even after making it writable.
>> Please
>> > let me know.
>> >
>> > Thanks,
>> > Om
>> >
>> >
>> >
>> > On Sun, Mar 17, 2013 at 10:48 PM, Om <bigosmallm@gmail.com (mailto:
>> bigosmallm@gmail.com)> wrote:
>> >
>> > > Here is David@Infra's response. This is the bug he is referring
>> to:[1]
>> > >
>> > > David,
>> > > > Folks outside the US are experiencing slowness in acccessing the git
>> > > > repos. Is this something that can/will be resolved?
>> > > > Also, what happens to the existing repos? Will they stay around as
>> > > > read-only forever? We are wondering if we can go back and look at
>> that if
>> > > > we find something missing in Git at a future date.
>> > > > How is the External git repo looking?
>> > > > Thanks,
>> > > > Om
>> > >
>> > >
>> > >
>> > >
>> > > David Nalley commented on INFRA-5549:
>> > > > -------------------------------------
>> > > > Om,
>> > > > I haven't spent anytime on External yet.
>> > > > SVN will stay RO forever once you migrate - hence the importance of
>> > > > diligence in the repo review. Once you begin forward movement,
>> remediating
>> > > > any differences is practically impossible.
>> > > > I suspect (but don't know) that the slowness is related to
>> INFRA-5939
>> > > > (ull provides the SSL front end to the git-wip-us, among others)
>> > > > I don't see anything that suggests it would manifest as slowness in
>> the
>> > > > machine that git-wip-us actually lives on.
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > Thanks,
>> > > Om
>> > >
>> > > [1] https://issues.apache.org/jira/browse/INFRA-5939
>> > >
>> > >
>> > >
>> > > On Sun, Mar 17, 2013 at 10:16 PM, Om <bigosmallm@gmail.com (mailto:
>> bigosmallm@gmail.com)> wrote:
>> > >
>> > > > On Sun, Mar 17, 2013 at 9:38 PM, Alex Harui <aharui@adobe.com(mailto:
>> aharui@adobe.com)> wrote:
>> > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > > On 3/17/13 9:22 PM, "Om" <bigosmallm@gmail.com (mailto:
>> bigosmallm@gmail.com)> wrote:
>> > > > >
>> > > > > > On Sun, Mar 17, 2013 at 9:09 PM, Alex Harui <aharui@adobe.com(mailto:
>> aharui@adobe.com)> wrote:
>> > > > > >
>> > > > > > > What does "fully tested" really mean? If a unix diff doesn't
>> find
>> > > > > anything
>> > > > > > > missing, isn't that sufficient?
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > That and the history, I guess.
>> > > > > We've spot checked history in all of the repos, haven't we? We
>> aren't
>> > > > > going
>> > > > > to spend the time to verify history on every file I hope.
>> > > >
>> > > >
>> > > > I just looked at the first and last log entry in each history.
>> > > >
>> > > >
>> > > > > BTW, what happens to our SVN repo? Does it go away or stay as
>> R/O? If
>> > > > > it
>> > > > > stays as R/O, then let's definitely open the git repos. Any
>> missing
>> > > > > history
>> > > > > is in SVN.
>> > > >
>> > > >
>> > > >
>> > > > I think it will stay on forever, but I have asked Infra just in
>> case.
>> > > >
>> > > >
>> > > > >
>> > > > > --
>> > > > > Alex Harui
>> > > > > Flex SDK Team
>> > > > > Adobe Systems, Inc.
>> > > > > http://blogs.adobe.com/aharui
>> > > >
>> > >
>> >
>>
>>
>>
>>
>

--bcaec54eee80bac49004d83bbbc2--