1 GIT v1.6.0 Release Notes
2 ========================
7 With the default Makefile settings, most of the programs are now
8 installed outside your $PATH, except for "git", "gitk", "git-gui" and
9 some server side programs that need to be accessible for technical
10 reasons. Invoking a git subcommand as "git-xyzzy" from the command
11 line has been deprecated since early 2006 (and officially announced in
12 1.5.4 release notes); use of them from your scripts after adding
13 output from "git --exec-path" to the $PATH is still supported in this
14 release, but users are again strongly encouraged to adjust their
15 scripts to use "git xyzzy" form, as we will stop installing
16 "git-xyzzy" hardlinks for built-in commands in later releases.
18 Source changes needed for porting to MinGW environment are now all in the
19 main git.git codebase.
21 By default, packfiles created with this version uses delta-base-offset
22 encoding introduced in v1.4.4. Pack idx files are using version 2 that
23 allows larger packs and added robustness thanks to its CRC checking,
26 GIT_CONFIG, which was only documented as affecting "git config", but
27 actually affected all git commands, now only affects "git config".
28 GIT_LOCAL_CONFIG, also only documented as affecting "git config" and
29 not different from GIT_CONFIG in a useful way, is removed.
31 The ".dotest" temporary area "git am" and "git rebase" use is now moved
32 inside the $GIT_DIR, to avoid mistakes of adding it to the project by
35 An ancient merge strategy "stupid" has been removed.
43 * git-p4 in contrib learned "allowSubmit" configuration to control on
44 which branch to allow "submit" subcommand.
46 * git-gui learned to stage changes per-line.
50 * Changes for MinGW port have been merged, thanks to Johannes Sixt and
53 * Sample hook scripts shipped in templates/ are now suffixed with
54 *.sample. We used to prevent them from triggering by default by
55 relying on the fact that we install them as unexecutable, but on
56 some filesystems this approach does not work. Instead of running
57 "chmod +x" on them, the users who want to activate these samples
58 as-is can now rename them dropping *.sample suffix.
60 * perl's in-place edit (-i) does not work well without backup files on Windows;
61 some tests are rewritten to cope with this.
65 * Updated howto/update-hook-example
67 * Got rid of usage of "git-foo" from the tutorial and made typography
70 * Disambiguating "--" between revs and paths is finally documented.
72 (performance, robustness, sanity etc.)
74 * index-pack used too much memory when dealing with a deep delta chain.
75 This has been optimized.
77 * reduced excessive inlining to shrink size of the "git" binary.
79 * verify-pack checks the object CRC when using version 2 idx files.
81 * When an object is corrupt in a pack, the object became unusable even
82 when the same object is available in a loose form, We now try harder to
83 fall back to these redundant objects when able. In particular, "git
84 repack -a -f" can be used to fix such a corruption as long as necessary
85 objects are available.
87 * Performance of "git-blame -C -C" operation is vastly improved.
89 * git-clone does not create refs in loose form anymore (it behaves as
90 if you immediately ran git-pack-refs after cloning). This will help
91 repositories with insanely large number of refs.
93 * core.fsyncobjectfiles configuration can be used to ensure that the loose
94 objects created will be fsync'ed (this is only useful on filesystems
95 that does not order data writes properly).
97 * "git commit-tree" plumbing can make Octopus with more than 16 parents.
98 "git commit" has been capable of this for quite some time.
100 (usability, bells and whistles)
102 * even more documentation pages are now accessible via "man" and "git help".
104 * A new environment variable GIT_CEILING_DIRECTORIES can be used to stop
105 the discovery process of the toplevel of working tree; this may be useful
106 when you are working in a slow network disk and are outside any working tree,
107 as bash-completion and "git help" may still need to run in these places.
109 * By default, stash entries never expire. Set reflogexpire in [gc
110 "refs/stash"] to a reasonable value to get traditional auto-expiration
113 * Longstanding latency issue with bash completion script has been
114 addressed. This will need to be backmerged to 'maint' later.
116 * pager.<cmd> configuration variable can be used to enable/disable the
117 default paging behaviour per command.
119 * "git-add -i" has a new action 'e/dit' to allow you edit the patch hunk
122 * git-am records the original tip of the branch in ORIG_HEAD before it
123 starts applying patches.
125 * git-apply can handle a patch that touches the same path more than once
126 much better than before.
128 * git-apply can be told not to trust the line counts recorded in the input
129 patch but recount, with the new --recount option.
131 * git-apply can be told to apply a patch to a path deeper than what the
132 patch records with --directory option.
134 * git-archive can be told to omit certain paths from its output using
135 export-ignore attributes.
137 * With -v option, git-branch describes the remote tracking statistics
138 similar to the way git-checkout reports by how many commits your branch
141 * git-branch's --contains option used to always require a commit parameter
142 to limit the branches with; it now defaults to list branches that
143 contains HEAD if this parameter is omitted.
145 * git-branch's --merged and --no-merged option used to always limit the
146 branches relative to the HEAD, but they can now take an optional commit
147 argument that is used in place of HEAD.
149 * git-bundle can read the revision arguments from the standard input.
151 * git-cherry-pick can replay a root commit now.
153 * git-clone can clone from a remote whose URL would be rewritten by
154 configuration stored in $HOME/.gitconfig now.
156 * git-diff --check now checks leftover merge conflict markers.
158 * When remote side used to have branch 'foo' and git-fetch finds that now
159 it has branch 'foo/bar', it refuses to lose the existing remote tracking
160 branch and its reflog. The error message has been improved to suggest
161 pruning the remote if the user wants to proceed and get the latest set
162 of branches from the remote, including such 'foo/bar'.
164 * fast-export learned to export and import marks file; this can be used to
165 interface with fast-import incrementally.
167 * git-rebase records the original tip of branch in ORIG_HEAD before it is
170 * "git rerere" can be told to update the index with auto-reused resolution
171 with rerere.autoupdate configuration variable.
173 * git-rev-list learned --children option to show child commits it
174 encountered during the traversal, instead of shoing parent commits.
176 * git-send-mail can talk not just over SSL but over TLS now.
178 * git-shortlog honors custom output format specified with "--pretty=format:".
180 * "git-stash save" learned --keep-index option. This lets you stash away the
181 local changes and bring the changes staged in the index to your working
182 tree for examination and testing.
184 * git-stash also learned branch subcommand to create a new branch out of
187 * git-status gives the remote tracking statistics similar to the way
188 git-checkout reports by how many commits your branch is ahead/behind.
190 * You can tell "git status -u" to even more aggressively omit checking
191 untracked files with --untracked-files=no.
193 * Original SHA-1 value for "update-ref -d" is optional now.
195 * Error codes from gitweb are made more descriptive where possible, rather
196 than "403 forbidden" as we used to issue everywhere.
200 * git-merge has been reimplemented in C.
206 All of the fixes in v1.5.6 maintenance series are included in
207 this release, unless otherwise noted.
211 O=v1.5.6.3-436-g1f8dc67
212 echo O=$(git describe refs/heads/master)
213 git shortlog --no-merges $O..refs/heads/master ^refs/heads/maint