提交 f1673dc4 编写于 作者: J Junio C Hamano

The first half of the seventh batch for 2.5

Signed-off-by: NJunio C Hamano <gitster@pobox.com>
上级 9fb0a798
...@@ -21,6 +21,17 @@ UI, Workflows & Features ...@@ -21,6 +21,17 @@ UI, Workflows & Features
chunks from Perforce, instead of making one call to "p4 changes" chunks from Perforce, instead of making one call to "p4 changes"
that may trigger "too many rows scanned" error from Perforce. that may trigger "too many rows scanned" error from Perforce.
* Unlike "$EDITOR" and "$GIT_EDITOR" that can hold the path to the
command and initial options (e.g. "/path/to/emacs -nw"), 'git p4'
did not let the shell interpolate the contents of the environment
variable that name the editor "$P4EDITOR" (and "$EDITOR", too).
This release makes it in line with the rest of Git, as well as with
Perforce.
* A new short-hand <branch>@{push} denotes the remote-tracking branch
that tracks the branch at the remote the <branch> would be pushed
to.
* "git show-branch --topics HEAD" (with no other arguments) did not * "git show-branch --topics HEAD" (with no other arguments) did not
do anything interesting. Instead, contrast the given revision do anything interesting. Instead, contrast the given revision
against all the local branches by default. against all the local branches by default.
...@@ -150,6 +161,9 @@ Performance, Internal Implementation, Development Support etc. ...@@ -150,6 +161,9 @@ Performance, Internal Implementation, Development Support etc.
the semantics of the option changed back in Git 1.9 days. the semantics of the option changed back in Git 1.9 days.
(merge 19d122b pt/pull-tags-error-diag later to maint). (merge 19d122b pt/pull-tags-error-diag later to maint).
* for_each_ref() callback functions were taught to name the objects
not with "unsigned char sha1[20]" but with "struct object_id".
Also contains various documentation updates and code clean-ups. Also contains various documentation updates and code clean-ups.
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册