gained a new member in the family (tab-in-indent) to help projects with
policy to indent only with spaces.
gained a new member in the family (tab-in-indent) to help projects with
policy to indent only with spaces.
* When working from a subdirectory, by default, git does not look for its
metadirectory ".git" across filesystems, primarily to help people who
have invocations of git in their custom PS1 prompts, as being outside
* When working from a subdirectory, by default, git does not look for its
metadirectory ".git" across filesystems, primarily to help people who
have invocations of git in their custom PS1 prompts, as being outside
* "git cvsserver" can be told to use pserver; its password file can be
stored outside the repository.
* "git cvsserver" can be told to use pserver; its password file can be
stored outside the repository.
* "git for-each-ref" learned "%(objectname:short)" that gives the object
name abbreviated.
* Various options to "git grep" (e.g. --count, --name-only) work better
with binary files.
* "git for-each-ref" learned "%(objectname:short)" that gives the object
name abbreviated.
* Various options to "git grep" (e.g. --count, --name-only) work better
with binary files.
* "git log --follow <path>" follows across copies (it used to only follow
renames). This may make the processing more expensive.
* "git log --follow <path>" follows across copies (it used to only follow
renames). This may make the processing more expensive.
* "git status [-s] --ignored" can be used to list ignored paths.
* Various "gitweb" enhancements and clean-ups, including syntax
* "git status [-s] --ignored" can be used to list ignored paths.
* Various "gitweb" enhancements and clean-ups, including syntax
* "git checkout" and "git rebase" overwrote paths that are marked "assume
unchanged" (aecda37c).
* "git clone/fetch/pull" issued an incorrect error message when a ref and
a symref that points to the ref were updated at the same time. This
obviously would update them to the same value, and should not result in
* "git checkout" and "git rebase" overwrote paths that are marked "assume
unchanged" (aecda37c).
* "git clone/fetch/pull" issued an incorrect error message when a ref and
a symref that points to the ref were updated at the same time. This
obviously would update them to the same value, and should not result in
* "git reset --hard" started from a wrong directory and a working tree in
a nonstandard location is in use got confused (560fb6a1).
* "git reset --hard" started from a wrong directory and a working tree in
a nonstandard location is in use got confused (560fb6a1).