1GIT v1.6.0 Release Notes 2======================== 3 4User visible changes 5-------------------- 6 7[[Note that none of these are not merged to 'master' as of this writing 8but they will be before 1.6.0 happens]] 9 10With default Makefile settings, most of the programs are now installed 11outside your $PATH, except for "git", "gitk", "git-gui" and some server 12side programs that needs to be accessible when connecting over ssh. 13 14When talking to remote repository over ssh, necessary server side programs 15are now invoked with "git $program" notation, not with "git-$program" 16notation. This should work with both servers running older git where you 17had all of these programs installed on $PATH, or newer git where you have 18only "git" on $PATH. However, if the remote side is running a custom 19software that restricts programs you can run over ssh, it might cause 20problems. Use --upload-pack="git-upload-pack" (when using ls-remote, 21fetch and pull on the client side), --receive-pack="git-receive-pack" 22(when using push on the client side), or --exec="git-upload-archive" (when 23using git-archive) as appropriate when talking to such a remote. 24 25Source changes needed for porting to MinGW environment are now all in the 26main git.git codebase. 27 28 29Updates since v1.5.6 30-------------------- 31 32(subsystems) 33 34(portability) 35 36* Sample hook scripts shipped in templates/ are now suffixed with 37 *.sample. We used to prevent them from triggering by default by 38 relying on the fact that we install them as unexecutable, but on 39 some filesystems this approach does not work. Instead of running 40 "chmod +x" on them, the users who want to activate these samples 41 as-is can now rename them dropping *.sample suffix. 42 43* perl's in-place edit (-i) does not work well without backup files on Windows; 44 some tests are rewritten to cope with this. 45 46(documentation) 47 48* Updated howto/update-hook-example 49 50(performance, robustness etc.) 51 52* reduced excessive inlining to shrink size of the "git" binary. 53 54* verify-pack checks the object CRC when using version 2 idx files. 55 56* When an object is corrupt in a pack, the object became unusable even 57 when the same object is available in a loose form, We now try harder to 58 fall back to these redundant objects when able. In particular, "git 59 repack -a -f" can be used to fix such a corruption as long as necessary 60 objects are available. 61 62* git-clone does not create refs in loose form anymore (it behaves as 63 if you immediately ran git-pack-refs after cloning). This will help 64 repositories with insanely large number of refs. 65 66* core.fsyncobjectfiles configuration can be used to ensure that the loose 67 objects created will be fsync'ed (this is only useful on filesystems 68 that does not order data writes properly). 69 70(usability, bells and whistles) 71 72* git-archive can be told to omit certain paths from its output using 73 export-ignore attributes. 74 75* fast-export learned to export and import marks file; this can be used to 76 interface with fast-import incrementally. 77 78* Original SHA-1 value for "update-ref -d" is optional now. 79 80* You can tell "git status -u" to even more aggressively omit checking 81 untracked files with --untracked-files=no. 82 83* Error codes from gitweb are made more descriptive where possible, rather 84 than "403 forbidden" as we used to issue everywhere. 85 86(internal) 87 88 89Fixes since v1.5.6 90------------------ 91 92All of the fixes in v1.5.6 maintenance series are included in 93this release, unless otherwise noted. 94 95 * diff -c/--cc showed unnecessary "deletion" lines at the context 96 boundary (needs backmerge to maint). 97 98 * "git-clone <src> <dst>" did not create leading directories for <dst> 99 like the scripted version used to do (needs backport to maint). 100 101--- 102exec >/var/tmp/1 103O=v1.5.6.1-77-gf9a08f6 104echo O=$(git describe refs/heads/master) 105git shortlog --no-merges $O..refs/heads/master ^refs/heads/maint