1Git v1.7.4 Release Notes (draft) 2================================ 3 4Updates since v1.7.3 5-------------------- 6 7 * The documentation Makefile now assumes by default asciidoc 8 and 8 docbook-xsl >= 1.73. If you have older versions, you can set 9 ASCIIDOC7 and ASCIIDOC_ROFF, respectively. 10 11 * The option parsers of various commands that create new branch (or 12 rename existing ones to a new name) were too loose and users were 13 allowed to call a branch with a name that begins with a dash by 14 creative abuse of their command line options, which only lead to 15 burn themselves. The name of a branch cannot begin with a dash 16 now. 17 18 * System-wide fallback default attributes can be stored in 19 /etc/gitattributes; core.attributesfile configuration variable can 20 be used to customize the path to this file. 21 22 * The thread structure generated by "git send-email" has changed 23 slightly. Setting the cover letter of the latest series as a reply 24 to the cover letter of the previous series with --in-reply-to used 25 to make the new cover letter and all the patches replies to the 26 cover letter of the previous series; this has been changed to make 27 the patches in the new series replies to the new cover letter. 28 29 * Bash completion script in contrib/ has been adjusted to be also 30 usable by zsh. 31 32 * Different pagers can be chosen depending on which subcommand is 33 being run under the pager, using "pager.<subcommand>" variable. 34 35 * The hardcoded tab-width of 8 used in whitespace breakage checks is now 36 configurable via the attributes mechanism. 37 38 * Support of case insensitive filesystems (i.e. "core.ignorecase") has 39 been improved. For example, the gitignore mechanism didn't pay attention 40 to the case insensitivity. 41 42 * The <tree>:<path> syntax to name a blob in a tree, and :<path> 43 syntax to name a blob in the index (e.g. "master:Makefile", 44 ":hello.c") have been extended. You can start <path> with "./" to 45 implicitly have the (sub)directory you are in prefixed to the 46 lookup. Similarly, ":../Makefile" from a subdirectory would mean 47 "the Makefile of the parent directory in the index". 48 49 * "git blame" learned --show-email option to display the e-mail 50 addresses instead of the names of authors. 51 52 * "git commit" learned --fixup and --squash options to help later invocation 53 of the interactive rebase. 54 55 * "git daemon" can be built in MinGW environment. 56 57 * "git daemon" can take more than one --listen option to listen to 58 multiple addresses. 59 60 * "git describe --exact-match" was optimized not to read commit 61 objects unnecessarily. 62 63 * "git diff" and "git grep" learned how functions and subroutines 64 in Fortran look like. 65 66 * "git fetch" learned "--recurse-submodules" option. 67 68 * "git mergetool" tells vim/gvim to show three-way diff by default 69 (use vimdiff2/gvimdiff2 as the tool name for old behaviour). 70 71 * "git log -G<pattern>" limits the output to commits whose change has 72 added or deleted lines that match the given pattern. 73 74 * "git read-tree" with no argument as a way to empty the index is 75 deprecated; we might want to remove it in the future. Users can 76 use the new --empty option to be more explicit instead. 77 78 * "git repack -f" does not spend cycles to recompress objects in the 79 non-delta representation anymore (use -F if you really mean it when 80 e.g. you changed the compression level). 81 82 * "git merge --log" used to limit the resulting merge log to 20 83 entries; this is now customizable by giving e.g. "--log=47". 84 85 * "git merge" may work better when all files were moved out of a 86 directory in one branch while a new file is created in place of that 87 directory in the other branch. 88 89 * "git rebase --autosquash" can use SHA-1 object names to name which 90 commit to fix up (e.g. "fixup! e83c5163"). 91 92 * The default "recursive" merge strategy learned --rename-threshold 93 option to influence the rename detection, similar to the -M option 94 of "git diff". E.g. "git merge -Xrename-threshold=50% ..." to use 95 this. 96 97 * The "recursive" strategy also learned to ignore various whitespace 98 changes; the most notable is -Xignore-space-at-eol. 99 100 * "git send-email" learned "--to-cmd", similar to "--cc-cmd", to read 101 recipient list from a command output. 102 103 * "git send-email" learned to read and use "To:" from its input files. 104 105 * you can extend "git shell", which is often used on boxes that allow 106 git-only login over ssh as login shell, with custom set of 107 commands. 108 109 * The current branch name in "git status" output can be colored differently 110 from the generic header color by setting "color.status.branch" variable. 111 112 * "git submodule sync" updates metainformation for all submodules, 113 not just the ones that have been checked out. 114 115 * gitweb can use custom 'highlight' command with its configuration file. 116 117 * other gitweb updates. 118 119 120Also contains various documentation updates. 121 122 123Fixes since v1.7.3 124------------------ 125 126All of the fixes in v1.7.3.X maintenance series are included in this 127release, unless otherwise noted. 128 129 * "git log --author=me --author=her" did not find commits written by 130 me or by her; instead it looked for commits written by me and by 131 her, which is impossible. 132 133 * "git merge" into an unborn branch removed an untracked file "foo" 134 from the working tree when merged branch had "foo" (2caf20c..172b642). 135 136 * "git push --progress" shows progress indicators now. 137 138 * "git repack" places its temporary packs under $GIT_OBJECT_DIRECTORY/pack 139 instead of $GIT_OBJECT_DIRECTORY/ to avoid cross directory renames. 140 141 * "git submodule update --recursive --other-flags" passes flags down 142 to its subinvocations. 143 144--- 145exec >/var/tmp/1 146O=v1.7.3.4-567-g38a5932 147echo O=$(git describe master) 148git shortlog --no-merges ^maint ^$O master