freshlybakedca.ke
Git fork
Git 1.7.10-rc4
Signed-off-by: Junio C Hamano <gitster@pobox.com>
+8
-8
+7
-7
Documentation/RelNotes/1.7.10.txt
+7
-7
Documentation/RelNotes/1.7.10.txt
···
32
32
* When you do not tell which branches and tags to push to the "git push"
33
33
command in any way, the command used "matching refs" rule to update
34
34
remote branches and tags with branches and tags with the same name you
35
-
locally have. In future versions of Git, this will change to use the
36
-
"upstream" rule to update the branch at the remote you would "pull"
37
-
from into your current branch with your local current branch. The
38
-
release after 1.7.10 will start issuing a warning about this change,
39
-
to encourage you to tell the command what to push out, e.g. by setting
40
-
push.default configuration.
35
+
locally have. In future versions of Git, this will change to push out
36
+
only your current branch according to either the "upstream" or the
37
+
"current" rule. Although "upstream" may be more powerful once the
38
+
user understands Git better, the semantics "current" gives is
39
+
simpler and easier to understand for beginners and may be a safer
40
+
and better default option, but we haven't decided yet.
41
41
42
42
43
43
Updates since v1.7.9
···
58
58
* Teams for localizing the messages from the Porcelain layer of
59
59
commands are starting to form, thanks to Jiang Xin who volunteered
60
60
to be the localization coordinator. Translated messages for
61
-
simplified Chinese and Swedish are available.
61
+
simplified Chinese, Swedish and Portuguese are available.
62
62
63
63
* The configuration mechanism learned an "include" facility; an
64
64
assignment to the include.path pseudo-variable causes the named