RF - make nisexts a native nibabel package rather than a subtree

Author: matthew-brett

Makefile

@@ -243,10 +243,5 @@ installed-tests:
 sdist-tests:
 	$(PYTHON) -c 'from nisext.testers import sdist_tests; sdist_tests("nibabel")'
 
-# Update nisext subtree from remote
-update-nisext:
-	git fetch nisext
-	git merge --squash -s subtree --no-commit nisext/master
-
 .PHONY: orig-src pylint
 

nisext/__init__.py

@@ -1,28 +1,7 @@
 # init for sext package
-""" Setuptools extensions that can be shared across projects
+""" Setuptools extensions
 
-Typical use for these routines is as a git subtree merge
-
-For example::
-
-    # Add a remote pointing to repository
-    git remote add nisext git://github.com/nipy/nisext.git
-    git fetch nisext
-    # Label nisext history as merged
-    git merge -s ours --no-commit nisext/master
-    # Read nisext contents as nisext subdirectory
-    git read-tree --prefix=nisext/ -u nisext/master
-    git commit -m "Merge nisext project as subtree"
-
-Then you would typically add a makefile target like::
-
-    # Update nisext subtree from remote
-    update-nisext:
-            git fetch nisext
-            git merge --squash -s subtree --no-commit nisext/master
-
-and commit when you have changes you want. This allows you to keep the nisext
-tree updated from the upstream repository, but the tree will be there and ready
-for someone without this machinery or remote.
+nibabel uses these routines, and houses them, and installs them.  nipy-proper
+and dipy use them.
 """