<
From version < 38.1 >
edited by msp
on 2012/10/16 15:04
To version < 40.1 >
edited by msp
on 2012/10/16 15:25
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -342,7 +342,8 @@
342 342  1*. If you don't have an SSH key: use the shell command {{code language="none"}}ssh-keygen{{/code}}, confirm the default destination file {{code language="none"}}~/.ssh/id_rsa{{/code}}, and choose whether to give a passphrase. If you have a passphrase, you need to enter it whenever you use your SSH key for the first time in a session. You can omit the passphrase, but that makes the key less secure. As result, the tool generates a private key {{code language="none"}}~/.ssh/id_rsa{{/code}}, which has to be kept secret, and a public key {{code language="none"}}~/.ssh/id_rsa.pub{{/code}}.
343 343  1. Go to //Projects// → //Create a new project// and call it "personal-<login>", replacing <login> with your own login name.
344 344  1. On the next page, create a repository named "turing" (or select //Add repository// on your project page).
345 -1. Once you are on the repository page, copy the URL shown in //Clone & push urls//.
345 +1. On the repository page, go to //Manage collaborators// → //Add collaborators// and add the user msp.
346 +1. Once you are back on the repository page, copy the URL shown in //Clone & push urls//.
346 346  1. Email the copied URL to [[msp@informatik.uni-kiel.de>>mailto:msp@informatik.uni-kiel.de||shape="rect"]]. This will serve as proof for your work on this tutorial.
347 347  1. (((
348 348  Transfer your {{code language="none"}}master{{/code}} branch to the new server-side repository. Replace the URL in the following command by the one copied from Gitorious:
... ... @@ -377,7 +377,7 @@
377 377  $ cd turing2
378 378  {{/noformat}}
379 379  
380 -The {{code language="none"}}clone{{/code}} command automatically creates a remote named {{code language="none"}}origin{{/code}} in the new local repository, which is set to the given URL.
381 +The {{code language="none"}}clone{{/code}} command automatically creates a remote named {{code language="none"}}origin{{/code}} in the new local repository, which is set to the given URL. You will use this second clone to simulate another user with access to the repository.
381 381  )))
382 382  1. Edit the file {{code language="none"}}examples.txt{{/code}} in the new clone ({{code language="none"}}turing2{{/code}}): replace {{code language="none"}}"a"{{/code}} in line 6 by {{code language="none"}}"c"{{/code}} and correct the tape representations in lines 9, 14, and 19 accordingly. Commit the change.
383 383  1. (((
... ... @@ -544,10 +544,10 @@
544 544   957f686..b58ded7 master -> master
545 545  {{/noformat}}
546 546  
547 -While {{code language="none"}}pull{{/code}} performs a {{code language="none"}}fetch{{/code}} and a {{code language="none"}}merge{{/code}}, {{code language="none"}}push{{/code}} transfers the new merged branch to the server. Note that during the merge operation conflicts can occur. In that case you have to resolve them and commit the changes before you can push.
548 +While {{code language="none"}}pull{{/code}} performs a {{code language="none"}}fetch{{/code}} and a {{code language="none"}}merge{{/code}}, {{code language="none"}}push{{/code}} transfers the new merged branch to the server. Note that during the merge operation conflicts can occur. In that case you have to resolve them and commit the changes before you can push. When used without parameters like shown above, {{code language="none"}}pull{{/code}} lookes in {{code language="none"}}.git/config{{/code}} to determine which branches to pull from which remotes.
548 548  )))
549 549  1. (((
550 -In order to check out the {{code language="none"}}sketches{{/code}} branch, which was previously pushed to the server, simply type the following command:
551 +In order to check out the {{code language="none"}}sketches{{/code}} branch locally, which was previously pushed to the server, simply type the following command:
551 551  
552 552  {{noformat}}
553 553  $ git checkout sketches
... ... @@ -555,7 +555,7 @@
555 555  Switched to a new branch 'sketches'
556 556  {{/noformat}}
557 557  
558 -This branch can be pushed and pulled with the server in the same way as you did for the {{code language="none"}}master{{/code}} branch.
559 +This branch can be pushed and pulled with the server in the same way as you did for the {{code language="none"}}master{{/code}} branch. Never check out {{code language="none"}}origin/sketches{{/code}}, since that is a remote tracking branch!
559 559  )))
560 560  
561 561  The {{code language="none"}}master{{/code}} branch should look like this:
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -2982159
1 +2982163
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/WS12EclPract/pages/2982159/Git
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/WS12EclPract/pages/2982163/Git