Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 36294D8AB for ; Fri, 23 Nov 2012 04:29:53 +0000 (UTC) Received: (qmail 21507 invoked by uid 500); 23 Nov 2012 04:29:52 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 21146 invoked by uid 500); 23 Nov 2012 04:29:51 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 21114 invoked by uid 99); 23 Nov 2012 04:29:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Nov 2012 04:29:50 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of webdoublefx@hotmail.com designates 65.55.111.92 as permitted sender) Received: from [65.55.111.92] (HELO blu0-omc2-s17.blu0.hotmail.com) (65.55.111.92) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Nov 2012 04:29:41 +0000 Received: from BLU162-DS14 ([65.55.111.71]) by blu0-omc2-s17.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 22 Nov 2012 20:29:20 -0800 X-Originating-IP: [82.247.153.175] X-EIP: [TxVR3E3jhKsTGgl+AaOILUjorvegYny4] X-Originating-Email: [webdoublefx@hotmail.com] Message-ID: From: =?iso-8859-1?Q?Fr=E9d=E9ric_THOMAS?= To: References: In-Reply-To: Subject: Re: Apache Flex SDK Developer Tool Suite (was: Say "Hi" to 5 (!) new Apache Flex Committers) Date: Fri, 23 Nov 2012 05:29:18 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3505.912 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3505.912 X-OriginalArrivalTime: 23 Nov 2012 04:29:20.0178 (UTC) FILETIME=[1B473920:01CDC933] X-Virus-Checked: Checked by ClamAV on apache.org Hi all, Just to inform I switched on svn as suggested. https://svn.apache.org/repos/asf/incubator/flex/whiteboard/fthomas/developerToolSuite/trunk/ - Fred. -----Message d'origine----- From: Fr�d�ric THOMAS Sent: Thursday, November 22, 2012 2:41 AM To: flex-dev@incubator.apache.org Subject: Re: Apache Flex SDK Developer Tool Suite (was: Say "Hi" to 5 (!) new Apache Flex Committers) Yes Nick, I undrestood and I will do that (even if I would have prefered to work on git, BTW, why Apache hasn't got a kind of subgit ? ) -----Message d'origine----- From: Nicholas Kwiatkowski Sent: Wednesday, November 21, 2012 7:54 PM To: flex-dev@incubator.apache.org Subject: Re: Apache Flex SDK Developer Tool Suite (was: Say "Hi" to 5 (!) new Apache Flex Committers) Would it be possible to setup your whiteboard space and work in there? That would still allow us to collaborate on the project without worrying about the rest of the side-effects. -Nick On Wed, Nov 21, 2012 at 10:35 AM, Fr�d�ric THOMAS wrote: > Hi Greg, > > This is almost what I want, ie make a POC and once approved specifications > and code, integrate it to the trunk, I do not see myself doing this POC > directly into the trunk, but it may being is what is recommended, just > that > it makes me weird that way, can you confirm me that I have to start a POC > in > the trunk ? > > Fred. > > -----Original Message----- > From: Greg Reddin [mailto:gredbug@gmail.com] > Sent: Wednesday, November 21, 2012 4:26 PM > To: flex-dev@incubator.apache.org > Subject: Re: Apache Flex SDK Developer Tool Suite (was: Say "Hi" to 5 (!) > new Apache Flex Committers) > > On Wed, Nov 21, 2012 at 2:52 AM, Fr�d�ric THOMAS > wrote: > > > Yes, I didn't put any Apache Header yet but I thought to add them at > > some point, this work if accepted has the goal to be re-integrated too > > (but, tell me if I can't do it), notwithstanding, I prefer to work on > > Git than svn, more flexible to me. > > > > The crux of the issue is that it needs to happen here if you want to > collaborate on it. We can't expect the developers to look in svn for one > person's work and look in github, etc. for someone else's work. We follow > commits in the Apache Subversion repo. Anything done elsewhere is not > really > part of the project until it gets checked in here. > >