Re: Question: git clone --no-checkout behavior

Bryan Turner [off-list ref] writes:

quoted

If you populated $GIT_DIR/index from the tree of HEAD, you would see
everything is deleted in the working tree.  You can simulate it by
doing this:

        git clone -n $over_there here
        cd here
        git read-tree HEAD
        git status

But it would not help people who want to check another branch out
immediately after cloning with -n, which is the whole point of the
option, so...

Is the reset call in my example in essence performing that same read-tree,
when it unstages the changes?

"git reset" (without any other parameters) reads the HEAD tree into
the index without touching the working tree, so I think it is
probably equivalent.