about summary refs log tree commit diff
path: root/third_party/git/Documentation/RelNotes/1.8.1.5.txt
diff options
context:
space:
mode:
Diffstat (limited to 'third_party/git/Documentation/RelNotes/1.8.1.5.txt')
-rw-r--r--third_party/git/Documentation/RelNotes/1.8.1.5.txt47
1 files changed, 0 insertions, 47 deletions
diff --git a/third_party/git/Documentation/RelNotes/1.8.1.5.txt b/third_party/git/Documentation/RelNotes/1.8.1.5.txt
deleted file mode 100644
index efa68aef22..0000000000
--- a/third_party/git/Documentation/RelNotes/1.8.1.5.txt
+++ /dev/null
@@ -1,47 +0,0 @@
-Git 1.8.1.5 Release Notes
-=========================
-
-Fixes since v1.8.1.4
---------------------
-
- * Given a string with a multi-byte character that begins with '-' on
-   the command line where an option is expected, the option parser
-   used just one byte of the unknown letter when reporting an error.
-
- * In v1.8.1, the attribute parser was tightened too restrictive to
-   error out upon seeing an entry that begins with an ! (exclamation),
-   which may confuse users to expect a "negative match", which does
-   not exist.  This has been demoted to a warning; such an entry is
-   still ignored.
-
- * "git apply --summary" has been taught to make sure the similarity
-   value shown in its output is sensible, even when the input had a
-   bogus value.
-
- * "git clean" showed what it was going to do, but sometimes ended
-   up finding that it was not allowed to do so, which resulted in a
-   confusing output (e.g. after saying that it will remove an
-   untracked directory, it found an embedded git repository there
-   which it is not allowed to remove).  It now performs the actions
-   and then reports the outcome more faithfully.
-
- * "git clone" used to allow --bare and --separate-git-dir=$there
-   options at the same time, which was nonsensical.
-
- * "git cvsimport" mishandled timestamps at DST boundary.
-
- * We used to have an arbitrary 32 limit for combined diff input,
-   resulting in incorrect number of leading colons shown when showing
-   the "--raw --cc" output.
-
- * The smart HTTP clients forgot to verify the content-type that comes
-   back from the server side to make sure that the request is being
-   handled properly.
-
- * "git help remote-helpers" failed to find the documentation.
-
- * "gitweb" pages served over HTTPS, when configured to show picon or
-   gravatar, referred to these external resources to be fetched via
-   HTTP, resulting in mixed contents warning in browsers.
-
-Also contains various documentation fixes.