[OpenLayers-Dev] Working on 3.0 git...

[Alexandre Dube]

Eric,

   Yep, that helped a lot.  Both pull requests are send too.

Thanks,

Alexandre


On 10-10-12 02:44 PM, Eric Lemoine wrote:
> On Tue, Oct 12, 2010 at 8:02 PM, Alexandre Dube<adube at mapgears.com>  wrote:
>    
>> Hi devs,
>>      
> Hi
>
> I'm not a github expert, but I'll try to answer your questions, hoping
> that others will correct my mistakes.
>
>
>    
>>   I started working on 3.0 tickets and got used with git for the first time.
>>   I have a couple of questions I'd like to ask, but first a small overview of
>> the situation : so far, I adopted a "one branch per ticket" strategy.  So
>> far, I did two (#522 and #1275) , i.e. I commited to my fork the fixes
>> needed for each one in their specific branch.  I was able to get the master
>> "upstream" repo to update mine as well.
>>
>> === what should I do now ? ===
>>
>>   Now, I'm just wondering what I should do with the work I did.  Should I
>> leave a note on the trac ticket even though it's not to be commited in svn ?
>>   Should I do nothing since the graph already demonstrate pretty much every
>> work done by everyone ?
>>      
> Let's say you're done with #1275. You can merge your "1275" branch
> into your master, and push this to your origin's master (your github
> repo). Once done you can do a pull request, for a core developer to
> pull your commits in the master of openlayers/openlayers.
>
>    
>> === where is my 522 branch ? ===
>>
>>   About the github network graph [1], I don't see yet the last branch with
>> its commit I just did.  Is there supposed to be any delay ?
>>      
> Maybe the branch exists in your local repository but not in your
> github repository. To create the branch in your github repository I
> think you can just push your commits to this branch as it existed:
>
> $ git push origin 522:522
>
> Hope it helps,
>
>    


-- 
Alexandre Dubé
Mapgears
www.mapgears.com