> On Mar 29, 2017, at 11:06 AM, Pavol Vaskovic <p...@pali.sk> wrote:
> 
> Thanks Max! That was very enlightening. One more question…
> 
> On 29 Mar 2017, at 19:57, Max Moiseev <mois...@apple.com 
> <mailto:mois...@apple.com>> wrote:
> 
>> [...]
>> cd swift
>> git checkout master
>> utils/update-checkout --scheme=master
>> git checkout -b my-new-branch
>> ... some work gets done …
>> git add .
>> git commit -m “Adding an absolutely awesome new feature”
>> git push mine my-new-branch # please note that I prefer to call my personal 
>> fork ‘mine’ whereas usually people call their fork remotes ‘origin’ and the 
>> upstream ‘upstream’.
>> open https://github.com/apple/swift <https://github.com/apple/swift>
> When/where/how did you switch from upstream to your own fork (after the 
> initial update-checkout)? Or am I misunderstanding how that works?
You don’t need to switch from one remote to the other. It is only a matter of 
where you get the updates from and push your changes to. Typically you would 
pull from the upstream (apple/swift) and push changes to origin (yourown/swift).

update-checkout script will call `git pull origin BRANCH_NAME` so, I guess my 
unusual approach to naming remotes works well in this case.

> 
> Best regards
> Pavol Vaskovic 

_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Reply via email to