Hello community,

here is the log from the commit of package git for openSUSE:12.3 checked in at 
2013-02-26 15:11:08
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:12.3/git (Old)
 and      /work/SRC/openSUSE:12.3/.git.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "git", Maintainer is "[email protected]"

Changes:
--------
--- /work/SRC/openSUSE:12.3/git/git.changes     2013-01-31 01:17:56.000000000 
+0100
+++ /work/SRC/openSUSE:12.3/.git.new/git.changes        2013-02-26 
15:11:14.000000000 +0100
@@ -1,0 +2,45 @@
+Wed Feb 20 17:26:15 CET 2013 - [email protected]
+
+- updated to version 1.8.1.4:
+ * "git imap-send" talking over imaps:// did make sure it received a
+   valid certificate from the other end, but did not check if the
+   certificate matched the host it thought it was talking to.
+
+  This fixes CVE-2013-0308, bnc#804730
+
+-------------------------------------------------------------------
+Sat Feb 16 02:19:25 UTC 2013 - [email protected]
+
+- updated to version 1.8.1.3:
+
+    * minor fixes and documentation updates.
+
+    more details, please see here:
+    https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.1.3.txt
+
+-------------------------------------------------------------------
+Wed Jan 30 01:57:15 UTC 2013 - [email protected]
+
+- updated to version 1.8.1.2:
+
+     * An element on GIT_CEILING_DIRECTORIES list that does not name the
+       real path to a directory (i.e. a symbolic link) could have caused
+       the GIT_DIR discovery logic to escape the ceiling.
+
+     * Command line completion for "tcsh" emitted an unwanted space
+       after completing a single directory name.
+
+     * Command line completion leaked an unnecessary error message while
+       looking for possible matches with paths in <tree-ish>.
+
+     * "git archive" did not record uncompressed size in the header when
+       streaming a zip archive, which confused some implementations of unzip.
+
+     * When users spelled "cc:" in lowercase in the fake "header" in the
+       trailer part, "git send-email" failed to pick up the addresses from
+       there. As e-mail headers field names are case insensitive, this
+       script should follow suit and treat "cc:" and "Cc:" the same way.
+
+    Also contains various documentation fixes.
+
+-------------------------------------------------------------------

Old:
----
  git-1.8.1.1.tar.gz

New:
----
  git-1.8.1.4.tar.gz

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

Other differences:
------------------
++++++ git.spec ++++++
--- /var/tmp/diff_new_pack.EgC78H/_old  2013-02-26 15:11:15.000000000 +0100
+++ /var/tmp/diff_new_pack.EgC78H/_new  2013-02-26 15:11:15.000000000 +0100
@@ -30,7 +30,7 @@
 BuildRequires:  python
 BuildRequires:  sgml-skel
 BuildRequires:  xmlto
-Version:        1.8.1.1
+Version:        1.8.1.4
 Release:        0
 Summary:        Fast, scalable, distributed revision control system
 License:        GPL-2.0

++++++ git-1.8.1.1.tar.gz -> git-1.8.1.4.tar.gz ++++++
++++ 4112 lines of diff (skipped)

++++++ git-bash-completion-egrep-color-fix.diff ++++++
--- /var/tmp/diff_new_pack.EgC78H/_old  2013-02-26 15:11:16.000000000 +0100
+++ /var/tmp/diff_new_pack.EgC78H/_new  2013-02-26 15:11:16.000000000 +0100
@@ -4,12 +4,12 @@
 
 --- a/contrib/completion/git-completion.bash
 +++ b/contrib/completion/git-completion.bash
-@@ -815,7 +815,7 @@ __git_complete_strategy ()
- __git_list_all_commands ()
- {
-       local i IFS=" "$'\n'
--      for i in $(git help -a|egrep '^  [a-zA-Z0-9]')
-+      for i in $(git help -a|egrep --color=never '^  [a-zA-Z0-9]')
-       do
-               case $i in
-               *--*)             : helper pattern;;
+@@ -538,7 +538,7 @@ __git_commands () {
+       then
+               printf "%s" "${GIT_TESTING_COMMAND_COMPLETION}"
+       else
+-              git help -a|egrep '^  [a-zA-Z0-9]'
++              git help -a|egrep --color=never '^  [a-zA-Z0-9]'
+       fi
+ }
+ 

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to