Loading README.md +6 −8 Original line number Diff line number Diff line Loading @@ -66,11 +66,11 @@ Homeworks are outdated and will be improved in the coming weeks. ### Class 2 homework **Deadline**: XX. February 2025, 23:59 **Deadline**: 11. March 2025, 23:59 * Create a new file in `class2_homework/` subdirectory of this repository with a name `<UCO>.txt`. Content of the file is up to you: it can be your favourite hobby, a cooking recipe, a book, ... a name `<UCO>.txt`. Write in this file what you'd like to see covered in the course or a suggest a topic for the last class. * Commit the change. * Push the change to your fork, **not** to the main branch (Hint: imagine a merge request would be a next step). Loading @@ -78,7 +78,7 @@ Homeworks are outdated and will be improved in the coming weeks. `git` binary invocations. Put the history in a new file `<UCO>_commands.txt` and place it in the same directory and the same branch, commit it and push it. We want to see how you use git so we're sure we're teaching effectively. This is how to directory should look: This is how the directory should look after you're done: ```bash $ tree class2_homework/ class2_homework Loading @@ -87,12 +87,10 @@ $ tree class2_homework/ 1 directory, 2 files $ cat class2_homework/* $ cat class2_homework/255490_commands.txt git foo git bar cat dog My favourite book series now is from Jeffery Deaver: Lincoln Rhyme. baz ``` Loading class2_homework/255490.txt +1 −1 Original line number Diff line number Diff line My favourite book series now is from Jeffery Deaver: Lincoln Rhyme. I'd like to see worktrees covered in class 6. class2_homework/255490_commands.txt +1 −1 Original line number Diff line number Diff line git foo git bar cat dog baz Loading
README.md +6 −8 Original line number Diff line number Diff line Loading @@ -66,11 +66,11 @@ Homeworks are outdated and will be improved in the coming weeks. ### Class 2 homework **Deadline**: XX. February 2025, 23:59 **Deadline**: 11. March 2025, 23:59 * Create a new file in `class2_homework/` subdirectory of this repository with a name `<UCO>.txt`. Content of the file is up to you: it can be your favourite hobby, a cooking recipe, a book, ... a name `<UCO>.txt`. Write in this file what you'd like to see covered in the course or a suggest a topic for the last class. * Commit the change. * Push the change to your fork, **not** to the main branch (Hint: imagine a merge request would be a next step). Loading @@ -78,7 +78,7 @@ Homeworks are outdated and will be improved in the coming weeks. `git` binary invocations. Put the history in a new file `<UCO>_commands.txt` and place it in the same directory and the same branch, commit it and push it. We want to see how you use git so we're sure we're teaching effectively. This is how to directory should look: This is how the directory should look after you're done: ```bash $ tree class2_homework/ class2_homework Loading @@ -87,12 +87,10 @@ $ tree class2_homework/ 1 directory, 2 files $ cat class2_homework/* $ cat class2_homework/255490_commands.txt git foo git bar cat dog My favourite book series now is from Jeffery Deaver: Lincoln Rhyme. baz ``` Loading
class2_homework/255490.txt +1 −1 Original line number Diff line number Diff line My favourite book series now is from Jeffery Deaver: Lincoln Rhyme. I'd like to see worktrees covered in class 6.
class2_homework/255490_commands.txt +1 −1 Original line number Diff line number Diff line git foo git bar cat dog baz