Start the post-1.8.4 cycle
It is tentatively called 1.8.5, but it should be an easy matter of renaming the release-notes file and RelNotes symlink to later call it 1.9 near the end of the cycle if we wanted to. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Aug 30, 2013 at 10:16 UTC
992c38644a4b001bdc89b5b5008fc5f6674ed5b7
3 files changed
+88
-2
Documentation/RelNotes/1.8.5.txt
new
+86
@@ -0,0 +1,86 @@
1
+Git v1.8.5 Release Notes
2
+========================
3
+
4
+Backward compatibility notes (for Git 2.0)
5
+------------------------------------------
6
+
7
+When "git push [$there]" does not say what to push, we have used the
8
+traditional "matching" semantics so far (all your branches were sent
9
+to the remote as long as there already are branches of the same name
10
+over there). In Git 2.0, the default will change to the "simple"
11
+semantics that pushes:
12
+
13
+ - only the current branch to the branch with the same name, and only
14
+ when the current branch is set to integrate with that remote
15
+ branch, if you are pushing to the same remote as you fetch from; or
16
+
17
+ - only the current branch to the branch with the same name, if you
18
+ are pushing to a remote that is not where you usually fetch from.
19
+
20
+Use the user preference configuration variable "push.default" to
21
+change this. If you are an old-timer who is used to the "matching"
22
+semantics, you can set the variable to "matching" to keep the
23
+traditional behaviour. If you want to live in the future early, you
24
+can set it to "simple" today without waiting for Git 2.0.
25
+
26
+When "git add -u" (and "git add -A") is run inside a subdirectory and
27
+does not specify which paths to add on the command line, it
28
+will operate on the entire tree in Git 2.0 for consistency
29
+with "git commit -a" and other commands. There will be no
30
+mechanism to make plain "git add -u" behave like "git add -u .".
31
+Current users of "git add -u" (without a pathspec) should start
32
+training their fingers to explicitly say "git add -u ."
33
+before Git 2.0 comes. A warning is issued when these commands are
34
+run without a pathspec and when you have local changes outside the
35
+current directory, because the behaviour in Git 2.0 will be different
36
+from today's version in such a situation.
37
+
38
+In Git 2.0, "git add <path>" will behave as "git add -A <path>", so
39
+that "git add dir/" will notice paths you removed from the directory
40
+and record the removal. Versions before Git 2.0, including this
41
+release, will keep ignoring removals, but the users who rely on this
42
+behaviour are encouraged to start using "git add --ignore-removal <path>"
43
+now before 2.0 is released.
44
+
45
+
46
+Updates since v1.8.4
47
+--------------------
48
+
49
+Foreign interfaces, subsystems and ports.
50
+
51
+
52
+UI, Workflows & Features
53
+
54
+ * "git whatchanged" may still be used by old timers, but mention of
55
+ it in documents meant for new users will only waste readers' time
56
+ wonderig what the difference is between it and "git log". Make it
57
+ less prominent in the general part of the documentation and explain
58
+ that it is merely a "git log" with different default behaviour in
59
+ its own document.
60
+
61
+
62
+Performance, Internal Implementation, etc.
63
+
64
+
65
+Also contains various documentation updates and code clean-ups.
66
+
67
+
68
+Fixes since v1.8.4
69
+------------------
70
+
71
+Unless otherwise noted, all the fixes since v1.8.4 in the maintenance
72
+track are contained in this release (see release notes to them for
73
+details).
74
+
75
+ * Some people still use rather old versions of bash, which cannot
76
+ grok some constructs like 'printf -v varname' the prompt and
77
+ completion code started to use recently.
78
+ (merge a44aa69 bc/completion-for-bash-3.0 later to maint).
79
+
80
+ * Code to read configuration from a blob object did not compile on
81
+ platforms with fgetc() etc. implemented as macros.
82
+ (merge 49d6cfa hv/config-from-blob later to maint-1.8.3).
83
+
84
+ * The recent "short-cut clone connectivity check" topic broke a
85
+ shallow repository when a fetch operation tries to auto-follow tags.
86
+ (merge 6da8bdc nd/fetch-pack-shallow-fix later to maint-1.8.3).
GIT-VERSION-GEN
+1
-1
@@ -1,7 +1,7 @@
1
#!/bin/sh
2
3
GVF=GIT-VERSION-FILE
4
-DEF_VER=v1.8.4
4
+DEF_VER=v1.8.4.GIT
5
6
LF='
7
'
RelNotes
+1
-1
@@ -1 +1 @@
1
-Documentation/RelNotes/1.8.4.txt
\ No newline at end of file
1
+Documentation/RelNotes/1.8.5.txt
\ No newline at end of file