2011年4月18日

[installer 2767] git-1.7.4.4

git-1.7.4.4 出ています。

☆ git-1.7.4.4
http://git-scm.com/
http://git-scm.com/download
http://www.kernel.org/pub/software/scm/git/git-1.7.4.4.tar.gz
ftp://ftp.kernel.org/pub/software/scm/git/git-1.7.4.4.tar.gz

Fixes since v1.7.4.3
--------------------

* Compilation of sha1_file.c on BSD platforms were broken due to our
recent use of getrlimit() without including <sys/resource.h>.

* "git config" did not diagnose incorrect configuration variable names.

* "git format-patch" did not wrap a long subject line that resulted from
rfc2047 encoding.

* "git instaweb" should work better again with plackup.

* "git log --max-count=4 -Sfoobar" now shows 4 commits that changes the
number of occurrences of string "foobar"; it used to scan only for 4
commits and then emitted only matching ones.

* "git log --first-parent --boundary $c^..$c" segfaulted on a merge.

* "git pull" into an empty branch should have behaved as if
fast-forwarding from emptiness to the version being pulled, with
the usual protection against overwriting untracked files.

* "git submodule" that is run while a merge in the superproject is in
conflicted state tried to process each conflicted submodule up to
three times.

* "git status" spent all the effort to notice racily-clean index entries
but didn't update the index file to help later operations go faster in
some cases.

And other minor fixes and documentation updates.


Fixes since v1.7.4.2
--------------------

* "git apply" used to confuse lines updated by previous hunks as lines
that existed before when applying a hunk, contributing misapplication
of patches with offsets.

* "git branch --track" (and "git checkout --track --branch") used to
allow setting up a random non-branch that does not make sense to follow
as the "upstream". The command correctly diagnoses it as an error.

* "git checkout $other_branch" silently removed untracked symbolic links
in the working tree that are in the way in order to check out paths
under it from the named branch.

* "git cvsimport" did not bail out immediately when the cvs server cannot
be reached, spewing unnecessary error messages that complain about the
server response that it never got.

* "git diff --quiet" did not work very well with the "--diff-filter"
option.

* "git grep -n" lacked a long-hand synonym --line-number.

* "git stash apply" reported the result of its operation by running
"git status" from the top-level of the working tree; it should (and
now does) run it from the user's working directory.

And other minor fixes and documentation updates.


Fixes since v1.7.4.1
--------------------

* Many documentation updates to match "git cmd -h" output and the
git-cmd manual page.

* We used to keep one file descriptor open for each and every packfile
that we have a mmap window on it (read: "in use"), even when for very
tiny packfiles. We now close the file descriptor early when the entire
packfile fits inside one mmap window.

* "git bisect visualize" tried to run "gitk" in windowing
environments even when "gitk" is not installed, resulting in a
strange error message.

* "git clone /no/such/path" did not fail correctly.

* "git commit" did not correctly error out when the user asked to use a
non existent file as the commit message template.

* "git diff --stat -B" ran on binary files counted the changes in lines,
which was nonsensical.

* "git diff -M" opportunistically detected copies, which was not
necessarily a good thing, especially when it is internally run by
recursive merge.

* "git difftool" didn't tell (g)vimdiff that the files it is reading are
to be opened read-only.

* "git merge" didn't pay attention to prepare-commit-msg hook, even
though if a merge is conflicted and manually resolved, the subsequent
"git commit" would have triggered the hook, which was inconsistent.

* "git patch-id" (and commands like "format-patch --ignore-in-upstream"
that use it as their internal logic) handled changes to files that end
with incomplete lines incorrectly.

* The official value to tell "git push" to push the current branch back
to update the upstream branch it forked from is now called "upstream".
The old name "tracking" is and will be supported.

* "git submodule update" used to honor the --merge/--rebase option (or
corresponding configuration variables) even for a newly cloned
subproject, which made no sense (so/submodule-no-update-first-time).

* gitweb's "highlight" interface mishandled tabs.

* gitweb didn't understand timezones with GMT offset that is not
multiple of a whole hour.

* gitweb had a few forward-incompatible syntactic constructs and
also used incorrect variable when showing the file mode in a diff.

And other minor fixes and documentation updates.

----
こがよういちろう


投稿者 xml-rpc : 2011年4月18日 16:08
役に立ちました?:
過去のフィードバック 平均:(0) 総合:(0) 投票回数:(0)
本記事へのTrackback: http://hoop.euqset.org/blog/mt-tb2006.cgi/103063
トラックバック
コメント
コメントする




画像の中に見える文字を入力してください。