Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion book/04-git-server/sections/git-on-a-server.asc
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
[[_git_on_the_server]]
[[_getting_git_on_a_server]]
=== Getting Git on a Server

Now we'll cover setting up a Git service running these protocols on your own server.
Expand Down
2 changes: 1 addition & 1 deletion book/04-git-server/sections/protocols.asc
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ Then, you can push to and pull from that remote as though you were doing so over
The pros of file-based repositories are that they're simple and they use existing file permissions and network access.
If you already have a shared filesystem to which your whole team has access, setting up a repository is very easy.
You stick the bare repository copy somewhere everyone has shared access to and set the read/write permissions as you would for any other shared directory.
We'll discuss how to export a bare repository copy for this purpose in <<_git_on_the_server>>.
We'll discuss how to export a bare repository copy for this purpose in <<_getting_git_on_a_server>>.

This is also a nice option for quickly grabbing work from someone else's working repository.
If you and a co-worker are working on the same project and they want you to check something out, running a command like `git pull /home/john/project` is often easier than them pushing to a remote server and you pulling down.
Expand Down