1Git v1.7.6 Release Notes (draft) 2======================== 3 4Updates since v1.7.5 5-------------------- 6 7 * Various git-svn updates. 8 9 * Updates the way content tags are handled in gitweb. 10 11 * Clean-up of the C part of i18n (but not l10n---please wait) 12 continues. 13 14 * Processes spawned by "[alias] <name> = !process" in the configuration 15 can inspect GIT_PREFIX environment variable to learn where in the 16 working tree the original command was invoked. 17 18 * "git blame" learned "--abbrev[=<n>]" option to control the minimum 19 number of hexdigits shown for commit object names. 20 21 * Aborting "git commit --interactive" discards updates to the index 22 made during the interctive session. 23 24 * "git commit" learned a "--patch" option to directly jump to the 25 per-hunk selection UI of the interactive mode. 26 27 * "git diff -C -C" used to disable the rename detection entirely when 28 there are too many copy candidate paths in the tree; now it falls 29 back to "-C" when doing so would keep the copy candidate paths 30 under the rename detection limit. 31 32 * "git diff" and its family of commands learned --dirstat=0 to show 33 directories that contribute less than 0.1% of changes. 34 35 * "git diff" and its family of commands learned --dirstat=lines mode to 36 assess damage to the directory based on number of lines in the patch 37 output, not based on the similarity numbers. 38 39 * "git format-patch" learned "--quiet" option to suppress the output of 40 the names of generated files. 41 42 * "git format-patch" quotes people's names when it has RFC822 special 43 characters in it, e.g. "Junio C. Hamano" <jch@example.com>. Earlier 44 it was up to the user to do this when using its output. 45 46 * "git log" and friends learned a new "--notes" option to replace the 47 "--show-notes" option. Unlike "--show-notes", "--notes=<ref>" does 48 not imply showing the default notes. 49 50 * "git merge" learned "-" as a short-hand for "the previous branch", just 51 like the way "git checkout -" works. 52 53 * "git merge" uses "merge.ff" configuration variable to decide to always 54 create a merge commit (i.e. --no-ff, aka merge.ff=no), refuse to create 55 a merge commit (i.e. --ff-only, aka merge.ff=only). Setting merge.ff=yes 56 (or not setting it at all) restores the default behaviour of allowing 57 fast-forward to happen when possible. 58 59 * "git rebase" that does not specify on top of which branch to rebase 60 the current branch now uses @{upstream} of the current branch. 61 62 * "git rev-list --count" used with "--cherry-mark" counts the cherry-picked 63 commits separately, producing more a useful output. 64 65 * "git submodule update" learned "--force" option to get rid of local 66 changes in submodules and replace them with the up-to-date version. 67 68 * Compressed tarball gitweb generates is made without the timestamp of 69 the tarball generation; snapshot from the same tree should result in 70 a same tarball. 71 72Also contains various documentation updates and minor miscellaneous 73changes. 74 75 76Fixes since v1.7.5 77------------------ 78 79Unless otherwise noted, all the fixes in 1.7.5.X maintenance track are 80included in this release. 81 82 * Setting $(prefix) in config.mak did not affect where etc/gitconfig 83 file is read from, even though passing it from the command line of 84 $(MAKE) did. 85 (merge kk/maint-prefix-in-config-mak later) 86 87 * The bash completion scripts should correctly work using zsh's bash 88 completion emulation layer now. 89 (merge either fc/completion-zsh later) 90 91 * "git config" used to choke with an insanely long line. 92 (merge ef/maint-strbuf-init later) 93 94 * "git send-pack" (hence "git push") over smalt-HTTP protocol could 95 deadlock when the client side pack-object died early. 96 (merge js/maint-send-pack-stateless-rpc-deadlock-fix later) 97 98--- 99exec >/var/tmp/1 100echo O=$(git describe master) 101O=v1.7.5.1-339-g254fd97 102git shortlog --no-merges ^maint ^$O master