summaryrefslogtreecommitdiff
path: root/devel/git-docs
diff options
context:
space:
mode:
authorryoon <ryoon>2015-07-04 05:56:29 +0000
committerryoon <ryoon>2015-07-04 05:56:29 +0000
commit266d706a6bebf2f3be09aa3d06ca3d851bc276ac (patch)
tree14723d824196a87a9f9230fd848e08114fc8702b /devel/git-docs
parenta18637617f06f22dd2fb3a9c9cec04c17099d9fc (diff)
downloadpkgsrc-266d706a6bebf2f3be09aa3d06ca3d851bc276ac.tar.gz
Update to 2.4.5
Changelog: Git v2.4.5 Release Notes ======================== Fixes since v2.4.4 ------------------ * The setup code used to die when core.bare and core.worktree are set inconsistently, even for commands that do not need working tree. * There was a dead code that used to handle "git pull --tags" and show special-cased error message, which was made irrelevant when the semantics of the option changed back in Git 1.9 days. * "color.diff.plain" was a misnomer; give it 'color.diff.context' as a more logical synonym. * The configuration reader/writer uses mmap(2) interface to access the files; when we find a directory, it barfed with "Out of memory?". * Recent "git prune" traverses young unreachable objects to safekeep old objects in the reachability chain from them, which sometimes showed unnecessary error messages that are alarming. * "git rebase -i" fired post-rewrite hook when it shouldn't (namely, when it was told to stop sequencing with 'exec' insn). Also contains typofixes, documentation updates and trivial code clean-ups. Git v2.4.4 Release Notes ======================== Fixes since v2.4.3 ------------------ * l10n updates for German. * An earlier leakfix to bitmap testing code was incomplete. * "git clean pathspec..." tried to lstat(2) and complain even for paths outside the given pathspec. * Communication between the HTTP server and http_backend process can lead to a dead-lock when relaying a large ref negotiation request. Diagnose the situation better, and mitigate it by reading such a request first into core (to a reasonable limit). * The clean/smudge interface did not work well when filtering an empty contents (failed and then passed the empty input through). It can be argued that a filter that produces anything but empty for an empty input is nonsense, but if the user wants to do strange things, then why not? * Make "git stash something --help" error out, so that users can safely say "git stash drop --help". * Clarify that "log --raw" and "log --format=raw" are unrelated concepts. * Catch a programmer mistake to feed a pointer not an array to ARRAY_SIZE() macro, by using a couple of GCC extensions. Also contains typofixes, documentation updates and trivial code clean-ups.
Diffstat (limited to 'devel/git-docs')
-rw-r--r--devel/git-docs/Makefile3
1 files changed, 1 insertions, 2 deletions
diff --git a/devel/git-docs/Makefile b/devel/git-docs/Makefile
index 78e2c4c169a..86fddbf3417 100644
--- a/devel/git-docs/Makefile
+++ b/devel/git-docs/Makefile
@@ -1,7 +1,6 @@
-# $NetBSD: Makefile,v 1.6 2015/06/12 10:48:49 wiz Exp $
+# $NetBSD: Makefile,v 1.7 2015/07/04 05:56:29 ryoon Exp $
PKGNAME= git-docs-${GIT_VERSION}
-PKGREVISION= 1
COMMENT= GIT Tree History Storage Tool (documentation)
CONFLICTS+= scmgit-docs-[0-9]*