diff options
author | adam <adam> | 2013-04-11 11:46:22 +0000 |
---|---|---|
committer | adam <adam> | 2013-04-11 11:46:22 +0000 |
commit | 9ea2eb7ce3234fd3f930f5a9b87bc1a3971d3ced (patch) | |
tree | d491f5b4a8384efe5842eb8e504d811b9305a460 /devel | |
parent | 480ae4adcd74efa9f42f1a1c3f61ff62a6525b5a (diff) | |
download | pkgsrc-9ea2eb7ce3234fd3f930f5a9b87bc1a3971d3ced.tar.gz |
Changes 1.8.2.1:
* An earlier change to the attribute system introduced at v1.8.1.2 by
mistake stopped a pattern "dir" (without trailing slash) from
matching a directory "dir" (it only wanted to allow pattern "dir/"
to also match).
* Verification of signed tags were not done correctly when not in C
or en/US locale.
* 'git commit -m "$msg"' used to add an extra newline even when
$msg already ended with one.
* The "--match=<pattern>" option of "git describe", when used with
"--all" to allow refs that are not annotated tags to be used as a
base of description, did not restrict the output from the command
to those that match the given pattern.
* An aliased command spawned from a bare repository that does not say
it is bare with "core.bare = yes" is treated as non-bare by mistake.
* When "format-patch" quoted a non-ascii strings on the header files,
it incorrectly applied rfc2047 and chopped a single character in
the middle of it.
* "git archive" reports a failure when asked to create an archive out
of an empty tree. It would be more intuitive to give an empty
archive back in such a case.
* "git tag -f <tag>" always said "Updated tag '<tag>'" even when
creating a new tag (i.e. not overwriting nor updating).
* "git cmd -- ':(top'" was not diagnosed as an invalid syntax, and
instead the parser kept reading beyond the end of the string.
* Annotated tags outside refs/tags/ hierarchy were not advertised
correctly to the ls-remote and fetch with recent version of Git.
* The code to keep track of what directory names are known to Git on
platforms with case insensitive filesystems can get confused upon a
hash collision between these pathnames and looped forever.
* The logic used by "git diff -M --stat" to shorten the names of
files before and after a rename did not work correctly when the
common prefix and suffix between the two filenames overlapped.
* "git submodule update", when recursed into sub-submodules, did not
acccumulate the prefix paths.
* "git am $maildir/" applied messages in an unexpected order; sort
filenames read from the maildir/ in a way that is more likely to
sort messages in the order the writing MUA meant to, by sorting
numeric segment in numeric order and non-numeric segment in
alphabetical order.
* When export-subst is used, "zip" output recorded incorrect
size of the file.
* Some platforms and users spell UTF-8 differently; retry with the
most official "UTF-8" when the system does not understand the
user-supplied encoding name that are the common alternative
spellings of UTF-8.
* "git branch" did not bother to check nonsense command line
parameters and issue errors in many cases.
* "git update-index -h" did not do the usual "-h(elp)" thing.
* perl/Git.pm::cat_blob slurped everything in core only to write it
out to a file descriptor, which was not a very smart thing to do.
* The SSL peer verification done by "git imap-send" did not ask for
Server Name Indication (RFC 4366), failing to connect SSL/TLS
sites that serve multiple hostnames on a single IP.
* "git index-pack" had a buffer-overflow while preparing an
informational message when the translated version of it was too
long.
* Clarify in the documentation "what" gets pushed to "where" when the
command line to "git push" does not say these explicitly.
* In "git reflog expire", REACHABLE bit was not cleared from the
correct objects.
* The "--color=<when>" argument to the commands in the diff family
was described poorly.
* The arguments given to pre-rebase hook were not documented.
* The v4 index format was not documented.
* The "--match=<pattern>" argument "git describe" takes uses glob
pattern but it wasn't obvious from the documentation.
* Some sources failed to compile on systems that lack NI_MAXHOST in
their system header (e.g. z/OS).
* Add an example use of "--env-filter" in "filter-branch"
documentation.
* "git bundle verify" did not say "records a complete history" for a
bundle that does not have any prerequisites.
* In the v1.8.0 era, we changed symbols that do not have to be global
to file scope static, but a few functions in graph.c were used by
CGit from sideways bypassing the entry points of the API the
in-tree users use.
* "git merge-tree" had a typo in the logic to detect d/f conflicts,
which caused it to segfault in some cases.
Diffstat (limited to 'devel')
-rw-r--r-- | devel/scmgit-base/distinfo | 8 | ||||
-rw-r--r-- | devel/scmgit/Makefile.version | 4 |
2 files changed, 6 insertions, 6 deletions
diff --git a/devel/scmgit-base/distinfo b/devel/scmgit-base/distinfo index 422feb63eac..530af00a620 100644 --- a/devel/scmgit-base/distinfo +++ b/devel/scmgit-base/distinfo @@ -1,8 +1,8 @@ -$NetBSD: distinfo,v 1.69 2013/04/08 14:12:25 mef Exp $ +$NetBSD: distinfo,v 1.70 2013/04/11 11:46:22 adam Exp $ -SHA1 (git-1.8.2.tar.gz) = 42960ec7c2d8404af3d3f6d21f32f1e97e6e0a96 -RMD160 (git-1.8.2.tar.gz) = 5bf37fa0f85b8b73691add594671f60b1a884fb6 -Size (git-1.8.2.tar.gz) = 4389957 bytes +SHA1 (git-1.8.2.1.tar.gz) = ad9f833e509ba31c83efe336fd3599e89a39394b +RMD160 (git-1.8.2.1.tar.gz) = 9f17311a8dc4d8f3192065b9db3420f2b0abed78 +Size (git-1.8.2.1.tar.gz) = 4400440 bytes SHA1 (patch-aa) = 47e743aedffe231477d82d1190787af64faaa4b4 SHA1 (patch-ac) = ae75c6ca3abb5edf688e4877f3df8b6c6297f091 SHA1 (patch-ae) = 9bc2e6c7f0a8fbc385b6ffda638d3245a62dc5ca diff --git a/devel/scmgit/Makefile.version b/devel/scmgit/Makefile.version index ecfaaff4c27..6d1e5157605 100644 --- a/devel/scmgit/Makefile.version +++ b/devel/scmgit/Makefile.version @@ -1,6 +1,6 @@ -# $NetBSD: Makefile.version,v 1.55 2013/04/08 14:12:25 mef Exp $ +# $NetBSD: Makefile.version,v 1.56 2013/04/11 11:46:22 adam Exp $ # # used by devel/scmgit/Makefile.common # used by www/gitweb/Makefile -GIT_VERSION= 1.8.2 +GIT_VERSION= 1.8.2.1 |