Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of rick.winscot@gmail.com
 designates 209.85.213.175 as permitted sender)
Date: Fri, 6 Jan 2012 14:10:07 -0500
From: Rick Winscot <rick.winscot@gmail.com>
To: flex-dev@incubator.apache.org
Message-ID: <CCF8F5FA86B74976A41EE105892B2797@gmail.com>
In-Reply-To: <CB2C7C49.39447%aharui@adobe.com>
References: <CB2C7C49.39447%aharui@adobe.com>
Subject: Re: Flex SDK code conventions
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="4f07470f_1f9d5c18_d14f"

--4f07470f_1f9d5c18_d14f
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Yes, past history should be preserved ( I'm not recommending that formatting be done prior to the first commit ). 

For clarification... after the initial commit of the SDK ( in its current state to preserve historical comparison - lets call this rev100 ) the source can be re-formatted to conform with established conventions. Formatting changes would then be committed at rev101 - this revision is the gold-standard moving forward. With that...

# developers can diff between revision rev000 - rev100 without issue
# developers can diff between revision rev101 - head without issue

If, by chance, developers need to diff between rev50 and rev200... all they have to do is take rev50 and format it which should give them an approximation of rev101. If there is any question - they can always do a three-way compare of rev50 (re-formatted), rev101, and rev200. Having one person do the re-formatting after the repository is in place... and committing the re-formatting changes in _1_ commit is the key.

Am I missing something? 

-- 
Rick Winscot


On Friday, January 6, 2012 at 1:24 PM, Alex Harui wrote:

> 
> 
> 
> On 1/6/12 10:05 AM, "Rick Winscot" <rick.winscot@gmail.com (mailto:rick.winscot@gmail.com)> wrote:
> 
> > If this path is followed...
> > 
> > #1 establish coding conventions
> > #2 commit SDK to SVN (as-is)
> > #3 run the code formatter against SDK
> > #4 commit / update reformatted code
> > #5 begin work on Apache Flex
> > 
> 
> Until you go back in history. We are trying to commit to SVN with past
> history.
> 
> -- 
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
> 
> 


--4f07470f_1f9d5c18_d14f--