Documentation/RelNotes-1.5.1.1.txt

   1 GIT v1.5.1.1 Release Notes
   2 ==========================
   3
   4 Fixes since v1.5.1
   5 ------------------
   6
   7 * Documentation updates
   8
   9   - The --left-right option of rev-list and friends is documented.
  10
  11   - The documentation for cvsimport has been majorly improved.
  12
  13   - "git-show-ref --exclude-existing" was documented.
  14
  15 * Bugfixes
  16
  17   - The implementation of -p option in "git cvsexportcommit" had
  18     the meaning of -C (context reduction) option wrong, and
  19     loosened the context requirements when it was told to be
  20     strict.
  21
  22   - "git cvsserver" did not behave like the real cvsserver when
  23     client side removed a file from the working tree without
  24     doing anything else on the path.  In such a case, it should
  25     restore it from the checked out revision.
  26
  27   - "git fsck" issued an alarming error message on detached
  28     HEAD.  It is not an error since at least 1.5.0.
  29
  30   - "git send-email" produced of References header of unbounded length;
  31     fixed this with line-folding.
  32
  33   - "git archive" to download from remote site should not
  34     require you to be in a git repository, but it incorrectly
  35     did.
  36
  37   - "git apply" ignored -p<n> for "diff --git" formatted
  38     patches.
  39
  40   - "git rerere" recorded a conflict that had one side empty
  41     (the other side adds) incorrectly; this made merging in the
  42     other direction fail to use previously recorded resolution.
  43
  44   - t4200 test was broken where "wc -l" pads its output with
  45     spaces.
  46
  47   - "git branch -m old new" to rename branch did not work
  48     without a configuration file in ".git/config".
  49
  50   - The sample hook for notification e-mail was misnamed.
  51
  52   - gitweb did not show type-changing patch correctly in the
  53     blobdiff view.
  54
  55   - git-svn did not error out with incorrect command line options.
  56
  57   - git-svn fell into an infinite loop when insanely long commit
  58     message was found.
  59
  60   - git-svn dcommit and rebase was confused by patches that were
  61     merged from another branch that is managed by git-svn.
  62
  63   - git-svn used to get confused when globbing remote branch/tag
  64     spec (e.g. "branches = proj/branches/*:refs/remotes/origin/*")
  65     is used and there was a plain file that matched the glob.