Hello community,

here is the log from the commit of package git for openSUSE:Factory checked in 
at 2018-03-29 11:49:09
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/git (Old)
 and      /work/SRC/openSUSE:Factory/.git.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "git"

Thu Mar 29 11:49:09 2018 rev:217 rq:591587 version:2.16.3

Changes:
--------
--- /work/SRC/openSUSE:Factory/git/git.changes  2018-03-09 10:35:14.951195419 
+0100
+++ /work/SRC/openSUSE:Factory/.git.new/git.changes     2018-03-29 
11:49:30.943559955 +0200
@@ -1,0 +2,39 @@
+Tue Mar 27 11:55:21 CEST 2018 - ku...@suse.de
+
+- Use %license instead of %doc [bsc#1082318]
+
+-------------------------------------------------------------------
+Fri Mar 23 03:12:14 UTC 2018 - avin...@opensuse.org
+
+- git 2.16.3:
+  * "git status" after moving a path in the working tree (hence
+    making it appear "removed") and then adding with the -N option
+    (hence making that appear "added") detected it as a rename, but
+    did not report the  old and new pathnames correctly.
+  * "git commit --fixup" did not allow "-m<message>" option to be
+    used at the same time; allow it to annotate resulting commit
+    with more text.
+  * When resetting the working tree files recursively, the working
+    tree of submodules are now also reset to match.
+  * Fix for a commented-out code to adjust it to a rather old API
+    change around object ID.
+  * When there are too many changed paths, "git diff" showed a
+    warning message but in the middle of a line.
+  * The http tracing code, often used to debug connection issues,
+    learned to redact potentially sensitive information from its
+    output so that it can be more safely sharable.
+  * Crash fix for a corner case where an error codepath tried to
+    unlock what it did not acquire lock on.
+  * The split-index mode had a few corner case bugs fixed.
+  * Assorted fixes to "git daemon".
+  * Completion of "git merge -s<strategy>" (in contrib/) did not
+    work well in non-C locale.
+  * Workaround for segfault with more recent versions of SVN.
+  * Recently introduced leaks in fsck have been plugged.
+  * Travis CI integration now builds the executable in 'script'
+    phase to follow the established practice, rather than during
+    'before_script' phase.  This allows the CI categorize the
+    failures better ('failed' is project's fault, 'errored' is
+    build environment's).
+
+-------------------------------------------------------------------

Old:
----
  git-2.16.2.tar.sign
  git-2.16.2.tar.xz

New:
----
  git-2.16.3.tar.sign
  git-2.16.3.tar.xz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ git.spec ++++++
--- /var/tmp/diff_new_pack.PoETNY/_old  2018-03-29 11:49:31.631535173 +0200
+++ /var/tmp/diff_new_pack.PoETNY/_new  2018-03-29 11:49:31.635535029 +0200
@@ -35,7 +35,7 @@
 %bcond_without docs
 
 Name:           git
-Version:        2.16.2
+Version:        2.16.3
 Release:        0
 Summary:        Fast, scalable, distributed revision control system
 License:        GPL-2.0-only
@@ -393,7 +393,7 @@
 fi
 
 mkdir -p "%buildroot/%_docdir/git" "%buildroot/%_docdir/git/howto" 
"%buildroot/%_docdir/git/technical"
-cp -a README.md COPYING Documentation/*.txt "%buildroot/%_docdir/git/"
+cp -a README.md Documentation/*.txt "%buildroot/%_docdir/git/"
 cp -a Documentation/howto/*.txt "%buildroot/%_docdir/git/howto/"
 cp -a Documentation/technical/*.txt "%buildroot/%_docdir/git/technical/"
 %{!?_without_docs: cp -a Documentation/*.html "%buildroot/%_docdir/git/"}
@@ -437,7 +437,6 @@
 %files doc
 %_docdir/%name/
 %exclude %_docdir/%name/README.md
-%exclude %_docdir/%name/COPYING
 
 %files svn
 %{gitexecdir}/*svn*
@@ -513,6 +512,6 @@
 %{_datadir}/tcsh
 /etc/profile.d/*.csh
 /etc/zsh_completion.d
-%doc %{_docdir}/%name/COPYING
+%license COPYING
 
 %changelog

++++++ git-2.16.2.tar.xz -> git-2.16.3.tar.xz ++++++
++++ 2573 lines of diff (skipped)



Reply via email to