Question: I want to run a [dokuwiki.org](https://www.dokuwiki.org/dokuwiki) on my server. I'm using the file-based setting so there's no external database involved.

I want to setup a git repository with contains dokuwiki's `data` directory so multiple committers are able to work offline and push the changes back when they are done. The `data` directory in the git repository is no big deal, you can set the location of the `data` directory using dokuwiki's config-files.

I used [this](http://toroid.org/ams/git-website-howto) guide to set everything up and it's working as expected.

tl;dr of the guide:

* setup `bare` repo
* `post-receive` hook on the bare repo to navigate to the `htdocs` directory and checkout the changes from the `bare` repo.
* you push something to the repo, and the `htdocs` directory automatically checksout the changes from the repo.

So the guide is only useful if you are using it for a static site or something database based. 

My problem is that the `www` directory is changed everytime someone edits something via the web-based wiki and not the files in their local repository -> the changes don't get pushed back to the `bare` repository because there's no hook/way/...to do that.

Is there anything i'm missing here or a better way to handle this usecase?

Answer: 
The purpose of adding a `using` directive is simply to allow you to use names within that namespace without fully-qualifying them.

So you don't *have* to add a `using` directive. You could write:

```
public static MvcHtmlString ObjectTable(this HtmlHelper helper, 
    ICollection<System.Object> objects, ICollection<string> header)

```

Or, as `object` is *always* an alias for `System.Object`, you could write:

```
public static MvcHtmlString ObjectTable(this HtmlHelper helper, 
    ICollection<object> objects, ICollection<string> header)

```

By the way, [not everything derives from object](http://blogs.msdn.com/b/ericlippert/archive/2009/08/06/not-everything-derives-from-object.aspx)...
Everything is derived from Object as you say, but System.Object is just like every other type that you want to reference in that you either have to reference it explicitly (I.e. System.Object) or by adding a using for the namespace. 

To have it behave otherwise would be inconsistent with the rest of .Net and would likely cause more confusion.