Merge branch 'js/shallow'

* js/shallow:
fetch-pack: Do not fetch tags for shallow clones.
get_shallow_commits: Avoid memory leak if a commit has been reached already.
git-fetch: Reset shallow_depth before auto-following tags.
upload-pack: Check for NOT_SHALLOW flag before sending a shallow to the client.
fetch-pack: Properly remove the shallow file when it becomes empty.
shallow clone: unparse and reparse an unshallowed commit
Why didn't we mark want_obj as ~UNINTERESTING in the old code?
Why does it mean we do not have to register shallow if we have one?
We should make sure that the protocol is still extensible.
add tests for shallow stuff
Shallow clone: do not ignore shallowness when following tags
allow deepening of a shallow repository
allow cloning a repository "shallowly"
support fetching into a shallow repository
upload-pack: no longer call rev-list

diff --cc Makefile
Simple merge

diff --cc git-fetch.sh
index 7fb47f69fb89156770919c70b7ac7e6fa75e92e5,5f316053fb9ad146546ed0718cc98b772c48b07f..8bd11f8b60c0ffec8a67f59bc7e12e1f63adfc91
--- 1/git-fetch.sh
--- 2/git-fetch.sh
+++ b/git-fetch.sh
@@@ -60,6 -60,16 +61,13 @@@ d
        -k|--k|--ke|--kee|--keep)
                keep='-k -k'
                ;;
 -      --reflog-action=*)
 -              rloga=`expr "z$1" : 'z-[^=]*=\(.*\)'`
 -              ;;
+       --depth=*)
+               shallow_depth="--depth=`expr "z$1" : 'z-[^=]*=\(.*\)'`"
+               ;;
+       --depth)
+               shift
+               shallow_depth="--depth=$1"
+               ;;
        -*)
                usage
                ;;