Hi Peter,

As Carlos says, we use github to host and share our patch, in order to we 
awaiting to Git real repo.

So just a mini fix on the patch syntax
[1]. 
If using Mac: curl -O https://github.com/apache/flex/pull/19.patch
If using Linux: wget https://github.com/apache/flex/pull/19.patch

[2]. patch -p1 < 19.patch

And if you browse If using Mac: curl -O https://github.com/apache/flex/pull/21, 
you can see the web mode of this pull-request, select diff tab and you may see 
the baseline images diff.


Thanks,

Jose


On Aug 29, 2012, at 11:24 PM, Carlos Rovira <carlos.rov...@codeoscopic.com> 
wrote:

> Peter,
> 
> you don't need git actually. We are waiting for this 2-4 weeks to get
> real Git on Apache Flex.
> Meanwhile Jose and I are using SVN and copy-paste the modifications in
> our respective fork in github
> since the layout folder is the same (actually).
> 
> So you only need to :
> 
> 1) dowload the patch using "curl -O <url-to-the patch>"
> 2) apply patch using "patch < -p1 <localy-saved-patch"
> 
> and you are ready to test :)
> 
> 
> 
> 
> 2012/8/29 Peter Ent <p...@adobe.com>:
>> Hi,
>> 
>> I'm new to git and while I've been reading about it, this will be my first
>> time using it and I'm having trouble understanding what I'm supposed to do
>> to apply this patch. Here's what I've done so far:
>> 
>> 1. git clone https://github.com/apache/flex
>> 2. git checkout -b FLEX-33177
>> 
>> Now I have a branch in which to work. Doing `git branch` shows me
>> 
>> * FLEX-33177
>>  trunk
>> 
>> 
>> So far it makes sense.
>> 
>> I'm confused by the pull-requests and the .patch files. I thought using
>> the .patch files makes sense, so I downloaded them but when I do, I get
>> many errors like this:
>> error: patch failed:
>> mustella/tests/mx/collections/AsyncListView/integration/AsyncListView_integ
>> ration_scrolling.mxml:69
>> error:
>> mustella/tests/mx/collections/AsyncListView/integration/AsyncListView_integ
>> ration_scrolling.mxml: patch does not apply
>> 
>> 
>> And I don't know what to do with the pull/19, pull/20, etc. I assume I use
>> `git pull` somehow, but I'm not sure.
>> 
>> Thanks in advance for your help and patience.
>> 
>> --peter
>> 
>> 
>> 
>> On 8/29/12 3:57 PM, "Jose Barragan (JIRA)" <j...@apache.org> wrote:
>> 
>>> 
>>>   [
>>> https://issues.apache.org/jira/browse/FLEX-33177?page=com.atlassian.jira.p
>>> lugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444363#com
>>> ment-13444363 ]
>>> 
>>> Jose Barragan commented on FLEX-33177:
>>> --------------------------------------
>>> 
>>> My  actual scenario is based of these news pull-requests:
>>> https://github.com/apache/flex/pull/19
>>> https://github.com/apache/flex/pull/20
>>> https://github.com/apache/flex/pull/21
>>> 
>>> I did activate the MX FTE Text compiler option in order to get the new
>>> font family in mx components, now all components adopt the new OpenSans
>>> font as you can see in baseline pull-request (21).
>>> 
>>> I did cancel the old pull-request 8,9,17 in favour of these:
>>> https://github.com/apache/flex/pull/19.patch
>>> https://github.com/apache/flex/pull/20.patch
>>> 
>>> The pull-request 21 exist only to share with you my new baseline image
>>> cuts, and the differences each other.
>>> 
>>> If this scenario seems OK, I will repair the new AssertPixelValues fails.
>>> 
>>>> Getting Mustella mx folder to Work
>>>> ----------------------------------
>>>> 
>>>>                Key: FLEX-33177
>>>>                URL: https://issues.apache.org/jira/browse/FLEX-33177
>>>>            Project: Apache Flex
>>>>         Issue Type: Improvement
>>>>         Components: .Unspecified - Framework
>>>>           Reporter: Jose Barragan
>>>>           Priority: Minor
>>>>             Labels: mustella, test
>>>> 
>>>> Getting the mustella "mx" folder tests, back to work
>>> 
>>> --
>>> This message is automatically generated by JIRA.
>>> If you think it was sent incorrectly, please contact your JIRA
>>> administrators
>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>> 
> 
> 
> 
> -- 
> Carlos Rovira
> Director de Tecnología
> M: +34 607 22 60 05
> F:  +34 912 35 57 77
> CODEOSCOPIC S.A.
> Avd. del General Perón, 32
> Planta 10, Puertas P-Q
> 28020 Madrid

Reply via email to