[ Sent upstream: https://gitlab.com/gitlab-org/gitlab-shell/merge_requests/40

  This was filed upstream but decided the better way to go is to
  configure default git templates to be just empty.

  Until we implement that, we continue to carry this patch as NXD ]

gitlab-shell uses completely own whole set of git hooks and just
symlinks repo.git/hooks to path/to/gitlab-shell/hooks/.

Original hooks that git added there - when initializing repository -
from its template, and which are by default deactivated, are currently
moved to repos.git/hooks.old.<timestamp>, e.g.

$ ls -F nexedi/helloweb.git/
    config
    description
    HEAD
    hooks@                  -->  ...path/to/gitlab-shell/hooks/
    hooks.old.1446564288/
    info/
    packed-refs
    refs/

$ ls -F nexedi/helloweb.git/hooks.old.1446564288/
    applypatch-msg.sample*
    post-update.sample*
    pre-commit.sample*
    pre-push.sample*
    update.sample*
    commit-msg.sample*
    pre-applypatch.sample*
    prepare-commit-msg.sample*
    pre-rebase.sample*

On the other hand, hooks.old.<timestamp> are not used anywhere and are
left there "just in case". But what is the point to keep those pristine
samples git creates by default? And we are sure those files are always
results of gitlab-shell initializing a repository, as it is
gitlab-shell's job to create/remove/update/etc repositories.

So do not keep old hooks, remove them.

P.S. The patch that introduced whole-hooks-dir-symlinking is
    db81327b (Symlink the whole hooks directory).

/cc @dzaporozhets, @jacobvosmaer

Prune during 'git gc' after all

See merge request !48

This reverts commit 1ca8a44f.

Never pruning loose objects at all is not really a solution for
anything, and it causes annoying `git gc --auto` warnings.

Add new command to list tags from a remote repo.

The output of the `git ls-remote` command is written to the STDOUT so
the client can read and parse the list of tags. If there is an error it's
also written to STDOUT.

Closes #39 

See merge request !47

The output of the `git ls-remote` command is written to the STDOUT so
the client can read and parse the list of tags. If there is an error it's
also written to STDOUT.

[ci skip]

Add the ability to fetch remote repo without tags.

When fetching remote repo with tags the new remote tags are mixed in
with the local tags (all tags are saved under refs/tags), this affects
the UI of the Project given that we're showing up tags of a remote repo.

REF: https://gitlab.com/gitlab-org/gitlab-ee/issues/116

See merge request !46

When fetching remote repo with tags the new remote tags are mixed in
with the local tags (all tags are saved under refs/tags), this affects
the UI of the Project given that we're showing up tags of a remote repo.

Use ssh key internal api to build the authorized-keys command on openssh 6.9

See merge request !42

This provides the integration point to the internal API to get the
ssh key from the internal API.

Add new required commands to update remote mirrors

Closes gitlab-org/gitlab-ee#116

See merge request !43

Fix git-annex issue when using SSH on a custom port

Easiest thing here is to use the full repo path on the server side.

Fixes https://gitlab.com/gitlab-org/gitlab-ee/issues/166

See merge request !45

Do not prune objects during 'git gc'

This is a workaround to reduce the impact of
https://gitlab.com/gitlab-org/gitlab-ce/issues/13524 .

See merge request !44

This is a workaround to reduce the impact of
https://gitlab.com/gitlab-org/gitlab-ce/issues/13524 .

[ci skip]

Added an optional --force parameter for gitlab-projects fetch-remote

The optional parameter will decide wheter to fetch using --force or not.
fetching with --force is a requirement for Gitlab Geo (https://gitlab.com/gitlab-org/gitlab-ee/issues/76) secondary node
replication.

This is a dependency for https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/179

See merge request !41

The optional parameter will decide wheter to fetch using --force or not.
fetching with --force is a requirement for Gitlab Geo secondary node
replication.

Update README.md

trivial spelling fix

workaround for webrick issue on ruby 2.2

Workaround that fixes https://gitlab.com/gitlab-org/gitlab-shell/issues/36

See merge request !38