OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/git?expand=0&rev=7

git.changes

@@ -1,3 +1,55 @@
+-------------------------------------------------------------------
+Wed Jan  9 00:42:47 CET 2008 - schwab@suse.de
+
+- Update to version 1.5.3.8.
+  * Some documentation used "email.com" as an example domain.
+  * git-svn fix to handle funky branch and project names going over
+    http/https correctly.
+  * git-svn fix to tone down a needlessly alarming warning message.
+  * git-clone did not correctly report errors while fetching over http.
+  * git-send-email added redundant Message-Id: header to the outgoing
+    e-mail when the patch text already had one.
+  * a read-beyond-end-of-buffer bug in configuration file updater was fixed.
+  * git-grep used to show the same hit repeatedly for unmerged paths.
+  * After amending the patch title in "git-am -i", the command did not
+    report the patch it applied with the updated title.
+
+-------------------------------------------------------------------
+Tue Jan  8 10:12:16 CET 2008 - crrodriguez@suse.de
+
+- git-cvsserver was unusable, it produced a perl failed-compilation error
+   due to missing dependency on perl-DBD-Sqlite.
+- update to version 1.5.3.7
+ * git-send-email added 8-bit contents to the payload without
+   marking it as 8-bit in a CTE header.
+ * "git-bundle create a.bndl HEAD" dereferenced the symref and
+   did not record the ref as 'HEAD'; this prevented a bundle
+   from being used as a normal source of git-clone.
+ * The code to reject nonsense command line of the form
+   "git-commit -a paths..." and "git-commit --interactive
+   paths..." were broken.
+ * Adding a signature that is not ASCII-only to an original
+   commit that is ASCII-only would make the result non-ASCII.
+   "git-format-patch -s" did not mark such a message correctly
+   with MIME encoding header.
+ * git-add sometimes did not mark the resulting index entry
+   stat-clean.  This affected only cases when adding the
+   contents with the same length as the previously staged
+   contents, and the previous staging made the index entry
+   "racily clean".
+ * git-commit did not honor GIT_INDEX_FILE the user had in the
+   environment.
+ * When checking out a revision, git-checkout did not report where the
+   updated HEAD is if you happened to have a file called HEAD in the
+   work tree.
+ * "git-rev-list --objects" mishandled a tree that points at a
+   submodule.
+ * "git cvsimport" was not ready for packed refs that "git gc" can
+   produce and gave incorrect results.
+ * Many scripted Porcelains were confused when you happened to have a
+   file called "HEAD" in your work tree.
+ 
+
 -------------------------------------------------------------------
 Wed Nov 28 09:12:23 CET 2007 - dmueller@suse.de