I put in the original FLAs from Adobe (they are binary files so didn't want
to put them in the main project) and a tool for converting FLAs to FXG.


On 3/18/13 12:09 PM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote:

> 1.  Migrate the External project to git
> 
> Why the External project is for ? I looked inside but never noticed it was
> here before today.
> 
> Thanks,
> -Fred
> 
> -----Message d'origine-----
> From: Om
> Sent: Monday, March 18, 2013 7:27 PM
> To: dev@flex.apache.org
> Subject: Re: [LAZY] Asking Infra to make all git repos read-write.
> 
> 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 <bigosma...@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 <bigosma...@gmail.com> wrote:
>> 
>>> On Sun, Mar 17, 2013 at 9:38 PM, Alex Harui <aha...@adobe.com> wrote:
>>> 
>>>> 
>>>> 
>>>> 
>>>> On 3/17/13 9:22 PM, "Om" <bigosma...@gmail.com> wrote:
>>>> 
>>>>> On Sun, Mar 17, 2013 at 9:09 PM, Alex Harui <aha...@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
>>>> 
>>>> 
>>> 
>> 
> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Reply via email to