| blob | db6956205d4fe12dbb4adefb71bc01030f15dde7 |
1 GIT v1.6.3 Release Notes
2 ========================
4 With the next major release, "git push" into a branch that is
5 currently checked out will be refused by default. You can choose
6 what should happen upon such a push by setting the configuration
7 variable receive.denyCurrentBranch in the receiving repository.
9 To ease the transition plan, the receiving repository of such a
10 push running this release will issue a big warning when the
11 configuration variable is missing. Please refer to:
13 http://git.or.cz/gitwiki/GitFaq#non-bare
14 http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
16 for more details on the reason why this change is needed and the
17 transition plan.
19 For a similar reason, "git push $there :$killed" to delete the branch
20 $killed in a remote repository $there, if $killed branch is the current
21 branch pointed at by its HEAD, gets a large warning. You can choose what
22 should happen upon such a push by setting the configuration variable
23 receive.denyDeleteCurrent in the receiving repository.
25 When the user does not tell "git push" what to push, it has always
26 pushed matching refs. For some people it is unexpected, and a new
27 configuration variable push.default has been introduced to allow
28 changing a different default behaviour. To advertise the new feature,
29 a big warning is issued if this is not configured and a git push without
30 arguments is attempted.
33 Updates since v1.6.2
34 --------------------
36 (subsystems)
38 (performance)
40 * many uses of lstat(2) in the codepath for "git checkout" have been
41 optimized out.
43 (usability, bells and whistles)
45 * rsync:/path/to/repo can be used to run git over rsync for local
46 repositories. It may not be useful in practice; meant primarily for
47 testing.
49 * http transport learned to prompt and use password when fetching from or
50 pushing to http://user@host.xz/ URL.
52 * (msysgit) progress output that is sent over the sideband protocol can
53 be handled appropriately in Windows console.
55 * "--pretty=<style>" option to the log family of commands can now be
56 spelled as "--format=<style>". In addition, --format=%formatstring
57 is a short-hand for --pretty=tformat:%formatstring.
59 * "--oneline" is a synonym for "--pretty=oneline --abbrev=commit".
61 * If you realize that you botched the patch when you are editing hunks
62 with the 'edit' action in git-add -i/-p, you can abort the editor to
63 tell git not to apply it.
65 * The number of commits shown in "you are ahead/behind your upstream"
66 messages given by "git checkout" and "git status" used to count merge
67 commits; now it doesn't.
69 * git-archive learned --output=<file> option.
71 * git-bisect shows not just the number of remaining commits whose goodness
72 is unknown, but also shows the estimated number of remaining rounds.
74 * You can give --date=<format> option to git-blame.
76 * git-branch -r shows HEAD symref that points at a remote branch in
77 interest of each tracked remote repository.
79 * git-config learned -e option to open an editor to edit the config file
80 directly.
82 * git-clone runs post-checkout hook when run without --no-checkout.
84 * git-fast-export choked when seeing a tag that does not point at commit.
86 * git-format-patch can be told to use attachment with a new configuration,
87 format.attach.
89 * git-format-patch can be told to produce deep or shallow message threads.
91 * git-format-patch learned format.headers configuration to add extra
92 header fields to the output. This behaviour is similar to the existing
93 --add-header=<header> option of the command.
95 * git-grep learned to highlight the found substrings in color.
97 * git-imap-send learned to work around Thunderbird's inability to easily
98 disable format=flowed with a new configuration, imap.preformattedHTML.
100 * git-rebase can be told to rebase the series even if your branch is a
101 descendant of the commit you are rebasing onto with --force-rebase
102 option.
104 * git-rebase can be told to report diffstat with the --stat option.
106 * Output from git-remote command has been vastly improved.
108 * git-repack (invoked from git-gc) did not work as nicely as it should in
109 a repository that borrows objects from neighbours via alternates
110 mechanism especially when some packs are marked with the ".keep" flag
111 to prevent them from being repacked.
113 * git-send-email learned --confirm option to review the Cc: list before
114 sending the messages out.
116 (developers)
118 * Test scripts can be run under valgrind.
120 * Test scripts can be run with installed git.
122 * Makefile learned 'coverage' option to run the test suites with
123 coverage tracking enabled.
125 * Building the manpages with docbook-xsl between 1.69.1 and 1.71.1 now
126 requires setting DOCBOOK_SUPPRESS_SP to work around a docbook-xsl bug.
127 This workaround used to be enabled by default, but causes problems
128 with newer versions of docbook-xsl. In addition, there are a few more
129 knobs you can tweak to work around issues with various versions of the
130 docbook-xsl package. See comments in Documentation/Makefile for details.
132 Fixes since v1.6.2
133 ------------------
135 All of the fixes in v1.6.2.X maintenance series are included in this
136 release, unless otherwise noted.
138 Here are fixes that this release has, but have not been backported to
139 v1.6.2.X series.
141 * The initial checkout did not read the attributes from the .gitattribute
142 file that is being checked out.
144 * git-gc spent excessive amount of time to decide if an object appears
145 in a locally existing pack (if needed, backport by merging 69e020a).
147 ---
148 exec >/var/tmp/1
149 O=v1.6.2.2-403-g8130949
150 echo O=$(git describe master)
151 git shortlog --no-merges $O..master ^maint