delta/gitlab/gitlab-shell.git, branch remove-hound-config

Remove hound config

2016-07-05T12:08:28+00:00

Merge branch 'user_stderr' into 'master'

2016-07-05T12:03:59+00:00


Use STDERR to output error messages

It's pretty minor change so I don't think we need a changelog item for this. 

Fixes https://gitlab.com/gitlab-org/gitlab-shell/issues/47

See merge request !68

use STDERR to output error messages

2016-07-05T09:50:37+00:00

Merge branch 'shards' into 'master'

2016-06-30T10:57:43+00:00


Implement shard paths handling

See https://gitlab.com/gitlab-org/gitlab-ee/issues/583

See merge request !61

Refactor repository paths handling to allow multiple git mount points

2016-06-29T17:58:20+00:00

Merge branch 'custom-hook-output' into 'master'

2016-06-26T06:41:18+00:00


Prevent blocking custom hook output streams

Based on https://gitlab.com/gitlab-org/gitlab-shell/merge_requests/49

Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/1458

See merge request !67

Simplify custom hook output handling

2016-06-24T09:49:38+00:00

Merge branch 'gitlab-redis' into 'master'

2016-06-23T16:51:42+00:00


Put Redis loading code in one place

Before this change you could not run the gitlab_net specs in isolation.

See merge request !64

Merge branch 'no-argf' into 'master'

2016-06-23T15:10:01+00:00


ARGF does more than we want

ARGF is a virtual IO stream that treats the elements of ARGV as paths
to files to be opened. In practice, git-receive-pack will probably
never pass arguments to pre-receive and post-receive because it is not
supposed to (according to 'man 5 githooks'). In case it does, however
our hooks should not have the surprise behavior of treating those
arguments as files to be opened.

See merge request !66

ARGF does more than we want

2016-06-23T14:59:57+00:00

ARGF is a virtual IO stream that treats the elements of ARGV as paths
to files to be opened. In practice, git-receive-pack will probably
never pass arguments to pre-receive and post-receive because it is not
supposed to (according to 'man 5 githooks'). In case it does, however
our hooks should not have the surprise behavior of treating those
arguments as files to be opened.