On Sat, May 17, 2014 at 9:01 AM, brian m. carlson
sand...@crustytoothpaste.net wrote:
On Tue, May 13, 2014 at 09:39:59AM +0200, Ákos, Tajti wrote:
Dear List,
we implemented our own git smart http server to be able to check permissions
and other thing before pushes. It works fine, however, the
On Mon, 2014-05-19 at 18:12 +1000, Bryan Turner wrote:
On Sat, May 17, 2014 at 9:01 AM, brian m. carlson
sand...@crustytoothpaste.net wrote:
On Tue, May 13, 2014 at 09:39:59AM +0200, Ákos, Tajti wrote:
Dear List,
we implemented our own git smart http server to be able to check
On Mon, May 19, 2014 at 06:12:10PM +1000, Bryan Turner wrote:
For starters, to return an error message, your status must be 200 OK.
You can't return any other status code or Git will interpret your
error as some form of _HTTP_ error rather than a _git_ error.
As of git v1.8.3, git will show
On Tue, May 13, 2014 at 09:39:59AM +0200, Ákos, Tajti wrote:
Dear List,
we implemented our own git smart http server to be able to check permissions
and other thing before pushes. It works fine, however, the error messages we
generate on the server side are not displayed by the command line
Dear List,
we implemented our own git smart http server to be able to check
permissions and other thing before pushes. It works fine, however, the
error messages we generate on the server side are not displayed by the
command line client. On the server we generate error messages like this:
5 matches
Mail list logo
