PNG  IHDR;IDATxܻn0K )(pA 7LeG{ §㻢|ذaÆ 6lذaÆ 6lذaÆ 6lom$^yذag5bÆ 6lذaÆ 6lذa{ 6lذaÆ `}HFkm,mӪôô! x|'ܢ˟;E:9&ᶒ}{v]n&6 h_tڠ͵-ҫZ;Z$.Pkž)!o>}leQfJTu іچ\X=8Rن4`Vwl>nG^is"ms$ui?wbs[m6K4O.4%/bC%t Mז -lG6mrz2s%9s@-k9=)kB5\+͂Zsٲ Rn~GRC wIcIn7jJhۛNCS|j08yiHKֶۛkɈ+;SzL/F*\Ԕ#"5m2[S=gnaPeғL lذaÆ 6l^ḵaÆ 6lذaÆ 6lذa; _ذaÆ 6lذaÆ 6lذaÆ RIENDB` Git v1.6.5.4 Release Notes ========================== Fixes since v1.6.5.3 -------------------- * "git help" (without argument) used to check if you are in a directory under git control. There was no breakage in behaviour per-se, but this was unnecessary. * "git prune-packed" gave progress output even when its standard error is not connected to a terminal; this caused cron jobs that run it to produce crufts. * "git pack-objects --all-progress" is an option to ask progress output from write-object phase _if_ progress output were to be produced, and shouldn't have forced the progress output. * "git apply -p --directory=" did not work well for a non-default value of n. * "git merge foo HEAD" was misparsed as an old-style invocation of the command and produced a confusing error message. As it does not specify any other branch to merge, it shouldn't be mistaken as such. We will remove the old style "git merge HEAD ..." syntax in future versions, but not in this release, * "git merge -m ..." added the standard merge message on its own after user-supplied message, which should have overridden the standard one. Other minor documentation updates are included.