aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2010-08-30 17:23:13 -0400
committerJoey Hess <joey@kitenet.net>2010-08-30 17:24:00 -0400
commit1b1c30a713f4e5273002a633c375821598974c05 (patch)
tree5635f10c7146f017ea8894001ef34ed0ef507ffe
parentf44306868c7d9de8133fcde754a727e387b1288a (diff)
downloadikiwiki-1b1c30a713f4e5273002a633c375821598974c05.tar
ikiwiki-1b1c30a713f4e5273002a633c375821598974c05.tar.gz
remove note about git-daemon bug
Seems to be fixed with git 1.7.1
-rw-r--r--doc/tips/untrusted_git_push.mdwn8
1 files changed, 0 insertions, 8 deletions
diff --git a/doc/tips/untrusted_git_push.mdwn b/doc/tips/untrusted_git_push.mdwn
index 3573a0ddf..b74e0e9d9 100644
--- a/doc/tips/untrusted_git_push.mdwn
+++ b/doc/tips/untrusted_git_push.mdwn
@@ -112,11 +112,3 @@ abort the push before refs are updated. However, the changeset will still
be present in your repository, wasting space. Since nothing refers to it,
it will be expired eventually. You can speed up the expiry by running `git
prune`.
-
-When aborting a push, ikiwiki displays an error message about why it didn't
-accept it. If using git over ssh, the user will see this error message,
-which is probably useful to them. But `git-daemon` is buggy, and hides this
-message from the user. This can make it hard for users to figure out why
-their push was rejected. (If this happens to you, look at "'git log --stat
-origin/master..`" and think about whether your changes would be accepted
-over the web interface.)