Browse files

Autogenerated HTML docs for v1.8.5.3-321-g14598

  • Loading branch information...
gitster committed Jan 13, 2014
1 parent 21bc18b commit bc8d4783cac3c942fc9e8cf2f3eae4aea8cab5cb
Showing with 820 additions and 704 deletions.
  1. +27 −0 RelNotes/
  2. +15 −0 RelNotes/1.9.txt
  3. +4 −0 config.txt
  4. +414 −407 git-config.html
  5. +35 −17 git-mv.html
  6. +12 −0 git-mv.txt
  7. +58 −43 git-rm.html
  8. +9 −0 git-rm.txt
  9. +72 −68 git.html
  10. +2 −1 git.txt
  11. +170 −166 technical/pack-heuristics.html
  12. +2 −2 technical/pack-heuristics.txt
@@ -0,0 +1,27 @@
+Git v1.8.5.3 Release Notes
+Fixes since v1.8.5.2
+ * The "--[no-]informative-errors" options to "git daemon" were parsed
+ a bit too loosely, allowing any other string after these option
+ names.
+ * A "gc" process running as a different user should be able to stop a
+ new "gc" process from starting.
+ * An earlier "clean-up" introduced an unnecessary memory leak to the
+ credential subsystem.
+ * "git mv A B/", when B does not exist as a directory, should error
+ out, but it didn't.
+ * "git rev-parse <revs> -- <paths>" did not implement the usual
+ disambiguation rules the commands in the "git log" family used in
+ the same way.
+ * "git cat-file --batch=", an admittedly useless command, did not
+ behave very well.
+Also contains typofixes, documentation updates and trivial code clean-ups.
@@ -90,6 +90,10 @@ Foreign interfaces, subsystems and ports.
UI, Workflows & Features
+ * Just like we give a reasonable default for "less" via the LESS
+ environment variable, we now specify a reasonable default for "lv"
+ via the "LV" environment variable when spawning the pager.
* Two-level configuration variable names in "branch.*" and "remote.*"
hierarchies, whose variables are predominantly three-level, were
not completed by hitting a <TAB> in bash and zsh completions.
@@ -154,6 +158,13 @@ UI, Workflows & Features
Performance, Internal Implementation, etc.
+ * When parsing a 40-hex string into the object name, the string is
+ checked to see if it can be interpreted as a ref so that a warning
+ can be given for ambiguity. The code kicked in even when the
+ core.warnambiguousrefs is set to false to squelch this warning, in
+ which case the cycles spent to look at the ref namespace were an
+ expensive no-op, as the result was discarded without being used.
* The naming convention of the packfiles has been updated; it used to
be based on the enumeration of names of the objects that are
contained in the pack, but now it also depends on how the packed
@@ -197,6 +208,10 @@ Unless otherwise noted, all the fixes since v1.8.5 in the maintenance
track are contained in this release (see the maintenance releases' notes
for details).
+ * The implementation of 'git stash $cmd "stash@{...}"' did not quote
+ the stash argument properly and left it split at IFS whitespace.
+ (merge 2a07e43 ow/stash-with-ifs later to maint).
* The "--[no-]informative-errors" options to "git daemon" were parsed
a bit too loosely, allowing any other string after these option
@@ -567,6 +567,10 @@ be passed to the shell by Git, which will translate the final
command to `LESS=FRSX less -+S`. The environment tells the command
to set the `S` option to chop long lines but the command line
resets it to the default to fold long lines.
+Likewise, when the `LV` environment variable is unset, Git sets it
+to `-c`. You can override this setting by exporting `LV` with
+another value or setting `core.pager` to `lv +c`.
A comma separated list of common whitespace problems to
Oops, something went wrong.

0 comments on commit bc8d478

Please sign in to comment.