index e529e11cb2d949b338a1f927e03634b2158ae32f..0668d3c0cadc8e252ae07e0f873f603fafa02c27 100644 (file)
* For people who need to import from Perforce, a front-end for
fast-import is in contrib/fast-import/.
* For people who need to import from Perforce, a front-end for
fast-import is in contrib/fast-import/.
-* Comes with git-gui 0.8.1.
+* Comes with git-gui 0.8.2.
* Comes with updated gitk.
* Comes with updated gitk.
- "git rev-list" learned --regexp-ignore-case and
--extended-regexp options to tweak its matching logic used
- "git rev-list" learned --regexp-ignore-case and
--extended-regexp options to tweak its matching logic used
- for --grep fitering.
+ for --grep filtering.
- "git describe --contains" is a handier way to call more
obscure command "git name-rev --tags".
- "git describe --contains" is a handier way to call more
obscure command "git name-rev --tags".
- "git send-email" can be told not to thread the messages when
sending out more than one patches.
- "git send-email" can be told not to thread the messages when
sending out more than one patches.
+ - "git send-email" can also be told how to find whom to cc the
+ message to for each message via --cc-cmd.
+
- "git config" learned NUL terminated output format via -z to
help scripts.
- "git config" learned NUL terminated output format via -z to
help scripts.
- "git clone" uses -l (hardlink files under .git) by default when
cloning locally.
- "git clone" uses -l (hardlink files under .git) by default when
cloning locally.
+ - URL used for "git clone" and friends can specify nonstandard SSH port
+ by using ssh://host:port/path/to/repo syntax.
+
- "git bundle create" can now create a bundle without negative refs,
i.e. "everything since the beginning up to certain points".
- "git bundle create" can now create a bundle without negative refs,
i.e. "everything since the beginning up to certain points".
recursively descends into trees by default.
- "git diff" does not show differences that come only from
recursively descends into trees by default.
- "git diff" does not show differences that come only from
- stat-dirtiness in the form of "diff --git" header anymore. When
- generating a textual diff, it shows a warning message at the end.
+ stat-dirtiness in the form of "diff --git" header anymore.
+ It runs "update-index --refresh" silently as needed.
+
+ - "git tag -l" used to match tags by globbing its parameter as if it
+ has wildcard '*' on both ends, which made "git tag -l gui" to match
+ tag 'gitgui-0.7.0'; this was very annoying. You now have to add
+ asterisk on the sides you want to wildcard yourself.
- The editor to use with many interactive commands can be
overridden with GIT_EDITOR environment variable, or if it
- The editor to use with many interactive commands can be
overridden with GIT_EDITOR environment variable, or if it
- "git log" learned --log-size to show the number of bytes in
the log message part of the output to help qgit.
- "git log" learned --log-size to show the number of bytes in
the log message part of the output to help qgit.
+ - "git log --name-status" does not require you to give "-r" anymore.
+ As a general rule, Porcelain commands should recurse when showing
+ diff.
+
+ - "git format-patch --root A" can be used to format everything
+ since the beginning up to A. This was supported with
+ "git format-patch --root A A" for a long time, but was not
+ properly documented.
+
- "git svn dcommit" retains local merge information.
- "git svnimport" allows an empty string to be specified as the
- "git svn dcommit" retains local merge information.
- "git svnimport" allows an empty string to be specified as the
- We used to have core.legacyheaders configuration, when
set to false, allowed git to write loose objects in a format
- We used to have core.legacyheaders configuration, when
set to false, allowed git to write loose objects in a format
- that mimicks the format used by objects stored in packs. It
+ that mimics the format used by objects stored in packs. It
turns out that this was not so useful. Although we will
continue to read objects written in that format, we do not
honor that configuration anymore and create loose objects in
turns out that this was not so useful. Although we will
continue to read objects written in that format, we do not
honor that configuration anymore and create loose objects in
small enough delta results it creates while looking for the
best delta candidates.
small enough delta results it creates while looking for the
best delta candidates.
- - "git pack-objects" learned a new heuristcs to prefer delta
+ - "git pack-objects" learned a new heuristic to prefer delta
that is shallower in depth over the smallest delta
possible. This improves both overall packfile access
performance and packfile density.
that is shallower in depth over the smallest delta
possible. This improves both overall packfile access
performance and packfile density.
when switching branches that have differences in only a
handful paths.
when switching branches that have differences in only a
handful paths.
- - "git commit paths..." has also been optimized.
-
+ - "git add paths..." and "git commit paths..." has also been
+ heavily optimized.
Fixes since v1.5.2
------------------
Fixes since v1.5.2
------------------
- "gitweb" had trouble handling non UTF-8 text with older
Encode.pm Perl module.
- "gitweb" had trouble handling non UTF-8 text with older
Encode.pm Perl module.
---
-exec >/var/tmp/1
-O=v1.5.3-rc6
-echo O=`git describe refs/heads/master`
-git shortlog --no-merges $O..refs/heads/master ^refs/heads/maint
+ - "git svn" misparsed the data from the commits in the repository when
+ the user had "color.diff = true" in the configuration. This has been
+ fixed.
+
+ - There was a case where "git svn dcommit" clobbered changes made on the
+ SVN side while committing multiple changes.
+
+ - "git-write-tree" had a bad interaction with racy-git avoidance and
+ gitattributes mechanisms.
+
+ - "git --bare command" overrode existing GIT_DIR setting and always
+ made it treat the current working directory as GIT_DIR.
+
+ - "git ls-files --error-unmatch" does not complain if you give the
+ same path pattern twice by mistake.
+
+ - "git init" autodetected core.filemode but not core.symlinks, which
+ made a new directory created automatically by "git clone" cumbersome
+ to use on filesystems that require these configurations to be set.
+
+ - "git log" family of commands behaved differently when run as "git
+ log" (no pathspec) and as "git log --" (again, no pathspec). This
+ inconsistency was introduced somewhere in v1.3.0 series but now has
+ been corrected.
+
+ - "git rebase -m" incorrectly displayed commits that were skipped.