Remote Repositories and Synchronization - Git Recipes - page 346

82d0a6b b2
6075835 b1
73e4416 a3
44fc529 a2
c8e56d1 a1
Repeat similar commands for Sarah's repository:
$ cd git-recipes/10-02/sarahs-repo
$ git log --oneline
The above command will print the output shown in Listing 10-2 .
Listing 10-2. The output of $ git log --oneline run in sarahs-repo from Figure 10-12
515710e Merge branch 'master' of ../shared-repo
596e379 b3
5d11316 a5
2f46c63 a4
82d0a6b b2
6075835 b1
73e4416 a3
44fc529 a2
c8e56d1 a1
Although the actual SHA-1 printed on your screen will be different you should no-
tice that both outputs are exactly the same. As you can guess the output of $ git
log executed in shared-repo from Figure 10-12 :
$ cd git-recipes/10-02/shared-repo
$ git log --oneline
also will be identical. The three databases stored in: johns-repo/.git/objects ,
sarahs-repo/.git/objects , and shared-repo/.git/objects contain
exactly the same objects. This is proved by the fact that the SHA-1 names returned by
$ git log in all three repositories are the same.
In other words when you send or receive revisions with $ git push or $ git
pull , git copies the database entries between the repositories. This is contrary to the $