Documentation / RelNotes-1.6.0.txton commit manpages: italicize command names in synopses (04c2407)
   1GIT v1.6.0 Release Notes
   2========================
   3
   4User visible changes
   5--------------------
   6
   7With the default Makefile settings, most of the programs are now
   8installed outside your $PATH, except for "git", "gitk", "git-gui" and
   9some server side programs that need to be accessible for technical
  10reasons.  Invoking a git subcommand as "git-xyzzy" from the command
  11line has been deprecated since early 2006 (and officially announced in
  121.5.4 release notes); use of them from your scripts after adding
  13output from "git --exec-path" to the $PATH is still supported in this
  14release, but users are again strongly encouraged to adjust their
  15scripts to use "git xyzzy" form, as we will stop installing
  16"git-xyzzy" hardlinks for built-in commands in later releases.
  17
  18Source changes needed for porting to MinGW environment are now all in the
  19main git.git codebase.
  20
  21By default, packfiles created with this version uses delta-base-offset
  22encoding introduced in v1.4.4.  Pack idx files are using version 2 that
  23allows larger packs and added robustness thanks to its CRC checking,
  24introduced in v1.5.2.
  25
  26
  27Updates since v1.5.6
  28--------------------
  29
  30(subsystems)
  31
  32* git-p4 in contrib learned "allowSubmit" configuration to control on
  33  which branch to allow "submit" subcommand.
  34
  35(portability)
  36
  37* Sample hook scripts shipped in templates/ are now suffixed with
  38  *.sample.  We used to prevent them from triggering by default by
  39  relying on the fact that we install them as unexecutable, but on
  40  some filesystems this approach does not work.  Instead of running
  41  "chmod +x" on them, the users who want to activate these samples
  42  as-is can now rename them dropping *.sample suffix.
  43
  44* perl's in-place edit (-i) does not work well without backup files on Windows;
  45  some tests are rewritten to cope with this.
  46
  47(documentation)
  48
  49* Updated howto/update-hook-example
  50
  51* Got rid of usage of "git-foo" from the tutorial.
  52
  53* Disambiguating "--" between revs and paths is finally documented.
  54
  55(performance, robustness, sanity etc.)
  56
  57* even more documentation pages are now accessible via "man" and "git help".
  58
  59* reduced excessive inlining to shrink size of the "git" binary.
  60
  61* verify-pack checks the object CRC when using version 2 idx files.
  62
  63* When an object is corrupt in a pack, the object became unusable even
  64  when the same object is available in a loose form,  We now try harder to
  65  fall back to these redundant objects when able.  In particular, "git
  66  repack -a -f" can be used to fix such a corruption as long as necessary
  67  objects are available.
  68
  69* git-clone does not create refs in loose form anymore (it behaves as
  70  if you immediately ran git-pack-refs after cloning).  This will help
  71  repositories with insanely large number of refs.
  72
  73* core.fsyncobjectfiles configuration can be used to ensure that the loose
  74  objects created will be fsync'ed (this is only useful on filesystems
  75  that does not order data writes properly).
  76
  77* "git commit-tree" plumbing can make Octopus with more than 16 parents.
  78  "git commit" has been capable of this for quite some time.
  79
  80(usability, bells and whistles)
  81
  82* git-apply can handle a patch that touches the same path more than once
  83  much better than before.
  84
  85* git-apply can be told not to trust the line counts recorded in the input
  86  patch but recount, with the new --recount option.
  87
  88* git-archive can be told to omit certain paths from its output using
  89  export-ignore attributes.
  90
  91* git-clone can clone from a remote whose URL would be rewritten by
  92  configuration stored in $HOME/.gitconfig now.
  93
  94* git-diff --check now checks leftover merge conflict markers.
  95
  96* When remote side used to have branch 'foo' and git-fetch finds that now
  97  it has branch 'foo/bar', it refuses to lose the existing remote tracking
  98  branch and its reflog.  The error message has been improved to suggest
  99  pruning the remote if the user wants to proceed and get the latest set
 100  of branches from the remote, including such 'foo/bar'.
 101
 102* fast-export learned to export and import marks file; this can be used to
 103  interface with fast-import incrementally.
 104
 105* Original SHA-1 value for "update-ref -d" is optional now.
 106
 107* git-send-mail can talk not just over SSL but over TLS now.
 108
 109* You can tell "git status -u" to even more aggressively omit checking
 110  untracked files with --untracked-files=no.
 111
 112* Error codes from gitweb are made more descriptive where possible, rather
 113  than "403 forbidden" as we used to issue everywhere.
 114
 115(internal)
 116
 117
 118Fixes since v1.5.6
 119------------------
 120
 121All of the fixes in v1.5.6 maintenance series are included in
 122this release, unless otherwise noted.
 123
 124 * diff -c/--cc showed unnecessary "deletion" lines at the context
 125   boundary (needs backmerge to maint).
 126
 127 * "git-clone <src> <dst>" did not create leading directories for <dst>
 128   like the scripted version used to do (needs backport to maint).
 129
 130---
 131exec >/var/tmp/1
 132O=v1.5.6.1-155-gaa0c1f2
 133echo O=$(git describe refs/heads/master)
 134git shortlog --no-merges $O..refs/heads/master ^refs/heads/maint