variable used to mean "do not require -f option to lose untracked
files", but we now use the safer default).
+ * The kinds of whitespace errors "git diff" and "git apply" notice (and
+ fix) can be controlled via 'core.whitespace' configuration variable
+ and 'whitespace' attribute in .gitattributes file.
+
* "git push" learned --dry-run option to show what would happen if a
push is run.
* "git bisect" learned "skip" action to mark untestable commits.
+ * "git bisect visualize" learned a shorter synonym "git bisect view".
+
+ * "git bisect visualize" runs "git log" in a non-windowed
+ environments. It also can be told what command to run (e.g. "git
+ bisect visualize tig").
+
* "git format-patch" learned "format.numbered" configuration variable
to automatically turn --numbered option on when more than one commits
are formatted.
* "git checkout" from a subdirectory learned to use "../path" to allow
checking out a path outside the current directory without cd'ing up.
+ * "git checkout" from and to detached HEAD leaves a bit more
+ information in the reflog.
+
* "git send-email --dry-run" shows full headers for easier diagnosis.
* "git merge-ours" is now built-in.
descriptive name from From: and Signed-off-by: lines in the commit
message.
- * "git status" from a subdirectory now shows relative paths which makes
- copy-and-pasting for git-checkout/git-add/git-rm easier.
-
- * "git checkout" from and to detached HEAD leaves a bit more
- information in the reflog.
+ * "git status" from a subdirectory now shows relative paths, which
+ makes copy-and-pasting for git-checkout/git-add/git-rm easier. The
+ traditional behaviour to show the full path relative to the top of
+ the work tree can be had by setting status.relativepaths
+ configuration variable to true.
* In addition there are quite a few internal clean-ups. Notably
--
exec >/var/tmp/1
-O=v1.5.3.7-1111-gd9f4059
+O=v1.5.3.7-1148-gcf7e147
echo O=`git describe refs/heads/master`
git shortlog --no-merges $O..refs/heads/master ^refs/heads/maint
<p>If there is no path that is different between the index file and\r
the current HEAD commit (i.e., there is nothing to commit by running\r
<tt>git-commit</tt>), the command exits with non-zero status.</p>\r
-<p>If any paths have been touched in the working tree (that is,\r
-their modification times have changed) but their contents and\r
-permissions are identical to those in the index file, the command\r
-updates the index file. Running <tt>git-status</tt> can thus speed up\r
-subsequent operations such as <tt>git-diff</tt> if the working tree\r
-contains many paths that have been touched but not modified.</p>\r
</div>\r
<h2>OUTPUT</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 09-Dec-2007 10:19:07 UTC\r
+Last updated 10-Dec-2007 10:07:20 UTC\r
</div>\r
</div>\r
</body>\r
the current HEAD commit (i.e., there is nothing to commit by running
`git-commit`), the command exits with non-zero status.
-If any paths have been touched in the working tree (that is,
-their modification times have changed) but their contents and
-permissions are identical to those in the index file, the command
-updates the index file. Running `git-status` can thus speed up
-subsequent operations such as `git-diff` if the working tree
-contains many paths that have been touched but not modified.
-
OUTPUT
------