lab 38 Review the Cloned Repository
- Learn about branches on remote repositories.
Look at the cloned repository 01
Let’s take a look at the cloned repository.
cd cloned_hello ls
$ cd cloned_hello $ ls README Rakefile lib
You should see a list of all the files in the top level of the original repository (
Review the Repository History 02
git hist --all
$ git hist --all * 2fae0b2 2013-04-13 | Updated Rakefile (HEAD, origin/master, origin/greet, origin/HEAD, master) [Jim Weirich] * 1c23048 2013-04-13 | Hello uses Greeter [Jim Weirich] * 62d7ce0 2013-04-13 | Added greeter class [Jim Weirich] * b59a8c2 2013-04-13 | Added README [Jim Weirich] * 96ee164 2013-04-13 | Added a Rakefile. [Jim Weirich] * 0f36766 2013-04-13 | Moved hello.rb to lib [Jim Weirich] * eb30103 2013-04-13 | Add an author/email comment [Jim Weirich] * 1f7ec5e 2013-04-13 | Added a comment (v1) [Jim Weirich] * 582495a 2013-04-13 | Added a default value (v1-beta) [Jim Weirich] * 323e28d 2013-04-13 | Using ARGV [Jim Weirich] * 9416416 2013-04-13 | First Commit [Jim Weirich]
You should now see a list of the all the commits in the new repository, and it should (more or less) match the history of commits in the original repository. The only difference should be in the names of the branches.
Remote branches 03
You should see a master branch (along with HEAD) in the history list. But you will also have number of strangely named branches (origin/master, origin/greet and origin/HEAD). We’ll talk about them in a bit.