Break up links with nested formating (rebased)

As per request: Post-receive hook should be owned by gitlab user, not git.

Potential solution for current `rake gitlab:app:backup_restore` issues.

Modified the `repo_dump` and `repo_restore` rake tasks to properly dump and restore repositories based on their `path` rather than their (project) `name`. The project name can be uppercase and may contain spaces. This caused the repository to be restored as a different `path` that it was initially created as, thus, breaking the `git remote` and the web interface can no longer detect the repository either because it searches by `path` and not by `name`. Also, when restoring the permissions are incorrect making it impossible to push new commits to the remote repository. So now on success it'll set the correct permissions (but requires that the `gitlab` user has `sudo` privileges, or this task must be executed as root).

Styled Wiki edit page

* don't show pointer cursor for for the whole list item any more
* fix hover color for links in .row_title

Merge branch 'add_wiki_comments' of git://github.com/seeingidog/gitlabhq into seeingidog-add_wiki_comments

Conflicts:
	app/controllers/admin/mailer_controller.rb
	app/controllers/notes_controller.rb

Use CommitDecorator more

Updated merge request subheading.

API changes

Handle LDAP missing credentials error with a flash message.

Create the githost.log file if necessary.

Issues API

Changed "authored or assigned to you" to read "authored by or assigned to you" which reads better.

This resolves issue #1121.
Signed-off-by: Pat Thoyts <patthoyts@users.sourceforge.net>

If a user fails to provide a username or password to the LDAP login
form then a 500 error is returned due to an exception being raised
in omniauth-ldap. This gem has been amended to use the omniauth
error propagation function (fail!) to pass this exception message to
the registered omniauth failure handler so that the Rails application
can handle it approriately.

The failure function now knows about standard exceptions and no longer
requires a specific check for the OmniAuth::Error exception added by
commit f322975c.

This resolves issue #1077.
Signed-off-by: Pat Thoyts <patthoyts@users.sourceforge.net>