1GIT v1.6.0 Release Notes 2======================== 3 4User visible changes 5-------------------- 6 7With the default Makefile settings, most of the programs are now 8installed outside your $PATH, except for "git", "gitk", "git-gui" and 9some server side programs that need to be accessible for technical 10reasons. Invoking a git subcommand as "git-xyzzy" from the command 11line has been deprecated since early 2006 (and officially announced in 121.5.4 release notes); use of them from your scripts after adding 13output from "git --exec-path" to the $PATH is still supported in this 14release, but users are again strongly encouraged to adjust their 15scripts to use "git xyzzy" form, as we will stop installing 16"git-xyzzy" hardlinks for built-in commands in later releases. 17 18Source changes needed for porting to MinGW environment are now all in the 19main git.git codebase. 20 21By default, packfiles created with this version uses delta-base-offset 22encoding introduced in v1.4.4. Pack idx files are using version 2 that 23allows larger packs and added robustness thanks to its CRC checking, 24introduced in v1.5.2. 25 26GIT_CONFIG, which was only documented as affecting "git config", but 27actually affected all git commands, now only affects "git config". 28GIT_LOCAL_CONFIG, also only documented as affecting "git config" and 29not different from GIT_CONFIG in a useful way, is removed. 30 31 32Updates since v1.5.6 33-------------------- 34 35(subsystems) 36 37* git-p4 in contrib learned "allowSubmit" configuration to control on 38 which branch to allow "submit" subcommand. 39 40(portability) 41 42* Sample hook scripts shipped in templates/ are now suffixed with 43 *.sample. We used to prevent them from triggering by default by 44 relying on the fact that we install them as unexecutable, but on 45 some filesystems this approach does not work. Instead of running 46 "chmod +x" on them, the users who want to activate these samples 47 as-is can now rename them dropping *.sample suffix. 48 49* perl's in-place edit (-i) does not work well without backup files on Windows; 50 some tests are rewritten to cope with this. 51 52(documentation) 53 54* Updated howto/update-hook-example 55 56* Got rid of usage of "git-foo" from the tutorial. 57 58* Disambiguating "--" between revs and paths is finally documented. 59 60(performance, robustness, sanity etc.) 61 62* even more documentation pages are now accessible via "man" and "git help". 63 64* reduced excessive inlining to shrink size of the "git" binary. 65 66* verify-pack checks the object CRC when using version 2 idx files. 67 68* When an object is corrupt in a pack, the object became unusable even 69 when the same object is available in a loose form, We now try harder to 70 fall back to these redundant objects when able. In particular, "git 71 repack -a -f" can be used to fix such a corruption as long as necessary 72 objects are available. 73 74* git-clone does not create refs in loose form anymore (it behaves as 75 if you immediately ran git-pack-refs after cloning). This will help 76 repositories with insanely large number of refs. 77 78* core.fsyncobjectfiles configuration can be used to ensure that the loose 79 objects created will be fsync'ed (this is only useful on filesystems 80 that does not order data writes properly). 81 82* "git commit-tree" plumbing can make Octopus with more than 16 parents. 83 "git commit" has been capable of this for quite some time. 84 85(usability, bells and whistles) 86 87* git-apply can handle a patch that touches the same path more than once 88 much better than before. 89 90* git-apply can be told not to trust the line counts recorded in the input 91 patch but recount, with the new --recount option. 92 93* git-archive can be told to omit certain paths from its output using 94 export-ignore attributes. 95 96* git-clone can clone from a remote whose URL would be rewritten by 97 configuration stored in $HOME/.gitconfig now. 98 99* git-diff --check now checks leftover merge conflict markers. 100 101* When remote side used to have branch 'foo' and git-fetch finds that now 102 it has branch 'foo/bar', it refuses to lose the existing remote tracking 103 branch and its reflog. The error message has been improved to suggest 104 pruning the remote if the user wants to proceed and get the latest set 105 of branches from the remote, including such 'foo/bar'. 106 107* fast-export learned to export and import marks file; this can be used to 108 interface with fast-import incrementally. 109 110* Original SHA-1 value for "update-ref -d" is optional now. 111 112* git-send-mail can talk not just over SSL but over TLS now. 113 114* You can tell "git status -u" to even more aggressively omit checking 115 untracked files with --untracked-files=no. 116 117* Error codes from gitweb are made more descriptive where possible, rather 118 than "403 forbidden" as we used to issue everywhere. 119 120(internal) 121 122 123Fixes since v1.5.6 124------------------ 125 126All of the fixes in v1.5.6 maintenance series are included in 127this release, unless otherwise noted. 128 129 * diff -c/--cc showed unnecessary "deletion" lines at the context 130 boundary (needs backmerge to maint). 131 132 * "git-clone <src> <dst>" did not create leading directories for <dst> 133 like the scripted version used to do (needs backport to maint). 134 135--- 136exec >/var/tmp/1 137O=v1.5.6.1-155-gaa0c1f2 138echo O=$(git describe refs/heads/master) 139git shortlog --no-merges $O..refs/heads/master ^refs/heads/maint