1 GIT v1.6.5 Release Notes
2 ========================
4 In git 1.7.0, which was planned to be the release after 1.6.5, "git
5 push" into a branch that is currently checked out will be refused by
8 You can choose what should happen upon such a push by setting the
9 configuration variable receive.denyCurrentBranch in the receiving
12 Also, "git push $there :$killed" to delete the branch $killed in a remote
13 repository $there, when $killed branch is the current branch pointed at by
14 its HEAD, will be refused by default.
16 You can choose what should happen upon such a push by setting the
17 configuration variable receive.denyDeleteCurrent in the receiving
20 To ease the transition plan, the receiving repository of such a
21 push running this release will issue a big warning when the
22 configuration variable is missing. Please refer to:
24 http://git.or.cz/gitwiki/GitFaq#non-bare
25 http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
27 for more details on the reason why this change is needed and the
35 * various updates to gitk, git-svn and gitweb.
39 * more improvements on mingw port.
41 * mingw will also give FRSX as the default value for the LESS
42 environment variable when the user does not have one.
44 * initial support to compile git on Windows with MSVC.
48 * On major platforms, the system can be compiled to use with Linus's
49 block-sha1 implementation of the SHA-1 hash algorithm, which
50 outperforms the default fallback implementation we borrowed from
53 * Unnecessary inefficiency in deepening of a shallow repository has
56 * "git clone" does not grab objects that it does not need (i.e.
57 referenced only from refs outside refs/heads and refs/tags
60 * The "git" main binary used to link with libcurl, which then dragged
61 in a large number of external libraries. When using basic plumbing
62 commands in scripts, this unnecessarily slowed things down. We now
63 implement http/https/ftp transfer as a separate executable as we
66 * "git clone" run locally hardlinks or copies the files in .git/ to
67 newly created repository. It used to give new mtime to copied files,
68 but this delayed garbage collection to trigger unnecessarily in the
69 cloned repository. We now preserve mtime for these files to avoid
72 (usability, bells and whistles)
74 * Human writable date format to various options, e.g. --since=yesterday,
75 master@{2000.09.17}, are taught to infer some omitted input properly.
77 * A few programs gave verbose "advice" messages to help uninitiated
78 people when issuing error messages. An infrastructure to allow
79 users to squelch them has been introduced, and a few such messages
82 * refs/replace/ hierarchy is designed to be usable as a replacement
83 of the "grafts" mechanism, with the added advantage that it can be
84 transferred across repositories.
86 * "git am" learned to optionally ignore whitespace differences.
88 * "git am" handles input e-mail files that has CRLF line endings sensibly.
90 * "git am" learned "--scissors" option to allow you to discard early part
91 of an incoming e-mail.
93 * "git archive -o output.zip" works without being told what format to
94 use with an explicit "--format=zip".option.
96 * "git checkout", "git reset" and "git stash" learned to pick and
97 choose to use selected changes you made, similar to "git add -p".
99 * "git clone" learned a "-b" option to pick a HEAD to check out
100 different from the remote's default branch.
102 * "git clone" learned --recursive option.
104 * "git clone" from a local repository on a different filesystem used to
105 copy individual object files without preserving the old timestamp, giving
106 them extra lifetime in the new repository until they gc'ed.
108 * "git commit --dry-run $args" is a new recommended way to ask "what would
109 happen if I try to commit with these arguments."
111 * "git commit --dry-run" and "git status" shows conflicted paths in a
112 separate section to make them easier to spot during a merge.
114 * "git cvsimport" now supports password-protected pserver access even
115 when the password is not taken from ~/.cvspass file.
117 * "git fast-export" learned --no-data option that can be useful when
118 reordering commits and trees without touching the contents of
121 * "git fast-import" has a pair of new front-end in contrib/ area.
123 * "git init" learned to mkdir/chdir into a directory when given an
124 extra argument (i.e. "git init this").
126 * "git instaweb" optionally can use mongoose as the web server.
128 * "git log --decorate" can optionally be told with --decorate=full to
129 give the reference name in full.
131 * "git merge" issued an unnecessarily scary message when it detected
132 that the merge may have to touch the path that the user has local
133 uncommitted changes to. The message has been reworded to make it
134 clear that the command aborted, without doing any harm.
136 * "git push" can be told to be --quiet.
138 * "git push" pays attention to url.$base.pushInsteadOf and uses a URL
139 that is derived from the URL used for fetching.
141 * informational output from "git reset" that lists the locally modified
142 paths is made consistent with that of "git checkout $another_branch".
144 * "git submodule" learned to give submodule name to scripts run with
145 "foreach" subcommand.
147 * various subcommands to "git submodule" learned --recursive option.
149 * "git submodule summary" learned --files option to compare the work
150 tree vs the commit bound at submodule path, instead of comparing
153 * "git upload-pack", which is the server side support for "git clone" and
154 "git fetch", can call a new post-upload-pack hook for statistics purposes.
158 * With GIT_TEST_OPTS="--root=/p/a/t/h", tests can be run outside the
159 source directory; using tmpfs may give faster turnaround.
161 * With NO_PERL_MAKEMAKER set, DESTDIR= is now honoured, so you can
162 build for one location, and install into another location to tar it
168 All of the fixes in v1.6.4.X maintenance series are included in this
169 release, unless otherwise noted.