Client exit whilst running pre-receive hook : commit accepted but no post-receive hook ran

Hi I have always assumed the post-receive hook to be executed whenever a commit is "accepted" by the (gitolite) server. That does not seem to be true any more. Since 9658846 is appears that, when a client bails out, the pre-receive hook continues to run and the commit is written to the repos

Re: using git-difftool -d when cherry-picking

On Sat, Apr 30, 2016 at 3:19 AM, David Aguilar wrote: > On Wed, Apr 27, 2016 at 11:12:25AM +0200, Jan Smets wrote: >> Hi >> >> Please consider following example >> >> #!/bin/bash >> rm -rf /tmp/gittest >> mkdir /tmp/gittest >> cd /tmp/gittest

using git-difftool -d when cherry-picking

Hi Please consider following example #!/bin/bash rm -rf /tmp/gittest mkdir /tmp/gittest cd /tmp/gittest git init echo $RANDOM > testfile git add testfile git commit -m test -a git branch X git checkout X echo $RANDOM > testfile git add testfile git commit -m test -a git checkout master echo $

git blame performance

Hi I have recently migrated a fairly large project from CVS to Git. One of the issues we're having is the blame/annotate performance. The repository contains +650k commits total, of which ~300k are on master. (raw size = ~8GB) Running blame on one of the oldest files takes over 30 seconds. Th

repository corruption when pushing commits to a repository running 'git gc --prune='

Hi I've recently expired my reflog to prune loose objects. On a live, bare, repository I ran 'git gc --prune=now' All clients ended up having problems, they would report: error: refs/heads/master does not point to a valid object! Running 'git log' on the bare repo gave : fatal: bad object HEA