Documentation / RelNotes / 2.3.5.txton commit Merge branch 'jk/notes-merge-from-anywhere' (1cb3ed3)
   1Git v2.3.5 Release Notes
   2========================
   3
   4Fixes since v2.3.4
   5------------------
   6
   7 * The prompt script (in contrib/) did not show the untracked sign
   8   when working in a subdirectory without any untracked files.
   9
  10 * Even though "git grep --quiet" is run merely to ask for the exit
  11   status, we spawned the pager regardless.  Stop doing that.
  12
  13 * Recommend format-patch and send-email for those who want to submit
  14   patches to this project.
  15
  16 * An failure early in the "git clone" that started creating the
  17   working tree and repository could have resulted in some directories
  18   and files left without getting cleaned up.
  19
  20 * "git fetch" that fetches a commit using the allow-tip-sha1-in-want
  21   extension could have failed to fetch all the requested refs.
  22
  23 * The split-index mode introduced at v2.3.0-rc0~41 was broken in the
  24   codepath to protect us against a broken reimplementation of Git
  25   that writes an invalid index with duplicated index entries, etc.
  26
  27 * "git prune" used to largely ignore broken refs when deciding which
  28   objects are still being used, which could spread an existing small
  29   damage and make it a larger one.
  30
  31 * "git tag -h" used to show the "--column" and "--sort" options
  32   that are about listing in a wrong section.
  33
  34 * The transfer.hiderefs support did not quite work for smart-http
  35   transport.
  36
  37 * The code that reads from the ctags file in the completion script
  38   (in contrib/) did not spell ${param/pattern/string} substitution
  39   correctly, which happened to work with bash but not with zsh.
  40
  41 * The explanation on "rebase --preserve-merges", "pull --rebase=preserve",
  42   and "push --force-with-lease" in the documentation was unclear.
  43
  44Also contains typofixes, documentation updates and trivial code clean-ups.