Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitaly.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'doc/serverside_git_usage.md')
-rw-r--r--doc/serverside_git_usage.md10
1 files changed, 1 insertions, 9 deletions
diff --git a/doc/serverside_git_usage.md b/doc/serverside_git_usage.md
index 889dc0035..823191bc6 100644
--- a/doc/serverside_git_usage.md
+++ b/doc/serverside_git_usage.md
@@ -1,9 +1,8 @@
# Server side Git usage
-Gitaly uses three implementations to read and write to Git repositories:
+Gitaly uses two implementations to read and write to Git repositories:
1. `git(1)` - The same Git used by clients all over the world
-1. [LibGit2](https://github.com/libgit2/libgit2) - a linkable library used through Rugged and Git2Go
1. On ad-hoc basis, part of Git is implemented in this repository if the
implementation is easy and stable. For example the [pktline](../internal/git/pktline) package.
@@ -39,10 +38,3 @@ interfaces. These make sure Gitaly is protected against command injection, the
correct `git` is used, and correct setup for observable command invocations are
used. When working with `git(1)` in Ruby, please be sure to read the
[Ruby shell scripting guide](https://docs.gitlab.com/ee/development/shell_commands.html).
-
-## Using LibGit2
-
-Gitaly uses [Git2Go](https://github.com/libgit2/git2go) for Golang, and
-[Rugged](https://github.com/libgit2/rugged) which both are thin adapters to call
-the C functions of LibGit2. Git2Go is always invoked through `cmd/gitaly-git2go`
-to mitigate issues with context cancellation and the potential for memory leaks.