summaryrefslogtreecommitdiff
path: root/devel/git-base/distinfo
diff options
context:
space:
mode:
authoradam <adam@pkgsrc.org>2015-01-19 15:42:42 +0000
committeradam <adam@pkgsrc.org>2015-01-19 15:42:42 +0000
commit1b13eae672cead44896a131864ab63bc55336612 (patch)
tree0074553f9c1e1dc7066a0d27b37ca2ff3d9c08df /devel/git-base/distinfo
parent78407bf07184405d12f8086b871e2c32de19b3ad (diff)
downloadpkgsrc-1b13eae672cead44896a131864ab63bc55336612.tar.gz
Changes 2.2.2:
* "git checkout $treeish $path", when $path in the index and the working tree already matched what is in $treeish at the $path, still overwrote the $path unnecessarily. * "git config --get-color" did not parse its command line arguments carefully. * open() emulated on Windows platforms did not give EISDIR upon an attempt to open a directory for writing. * A few code paths used abs() when they should have used labs() on long integers. * "gitweb" used to depend on a behaviour recent CGI.pm deprecated. * "git init" (hence "git clone") initialized the per-repository configuration file .git/config with x-bit by mistake. * Git 2.0 was supposed to make the "simple" mode for the default of "git push", but it didn't. * "Everyday" document had a broken link. * The build procedure did not bother fixing perl and python scripts when NO_PERL and NO_PYTHON build-time configuration changed. * The code that reads the reflog from the newer to the older entries did not handle an entry that crosses a boundary of block it uses to read them correctly. * "git apply" was described in the documentation to take --ignore-date option, which it does not. * Traditionally we tried to avoid interpreting date strings given by the user as future dates, e.g. GIT_COMMITTER_DATE=2014-12-10 when used early November 2014 was taken as "October 12, 2014" because it is likely that a date in the future, December 10, is a mistake. This heuristics has been loosened to allow people to express future dates (most notably, --until=<date> may want to be far in the future) and we no longer tiebreak by future-ness of the date when (1) ISO-like format is used, and (2) the string can make sense interpreted as both y-m-d and y-d-m. Git may still have to use the heuristics to tiebreak between dd/mm/yy and mm/dd/yy, though. * The code to abbreviate an object name to its short unique prefix has been optimized when no abbreviation was requested. * "git add --ignore-errors ..." did not ignore an error to give a file that did not exist. * Git did not correctly read an overlong refname from a packed refs file. Also contains typofixes, documentation updates and trivial code clean-ups.
Diffstat (limited to 'devel/git-base/distinfo')
-rw-r--r--devel/git-base/distinfo8
1 files changed, 4 insertions, 4 deletions
diff --git a/devel/git-base/distinfo b/devel/git-base/distinfo
index 68970c06cbd..dea54606699 100644
--- a/devel/git-base/distinfo
+++ b/devel/git-base/distinfo
@@ -1,8 +1,8 @@
-$NetBSD: distinfo,v 1.21 2014/12/19 00:49:53 schmonz Exp $
+$NetBSD: distinfo,v 1.22 2015/01/19 15:42:42 adam Exp $
-SHA1 (git-2.2.1.tar.xz) = b9be1448c5db065f8fda875abd224f2fef1d32bc
-RMD160 (git-2.2.1.tar.xz) = 36087561134c261fc5b444017861a86636eadaa3
-Size (git-2.2.1.tar.xz) = 3590808 bytes
+SHA1 (git-2.2.2.tar.xz) = 013649d20f8f4d44e8b2aacdb3a8a348ecb42346
+RMD160 (git-2.2.2.tar.xz) = 6a5800138575ae5148e7e62f0930e79ab216914f
+Size (git-2.2.2.tar.xz) = 3592264 bytes
SHA1 (patch-aa) = 8c1096065d26b93a6e10bc6926d3fc3686f711f2
SHA1 (patch-ac) = 376cdd1c58b143c820ff6395987a8a77cf9b52ba
SHA1 (patch-ae) = 9bc2e6c7f0a8fbc385b6ffda638d3245a62dc5ca