Server IP : 15.235.198.142 / Your IP : 216.73.216.66 Web Server : Apache/2.4.58 (Ubuntu) System : Linux ballsack 6.8.0-45-generic #45-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 30 12:02:04 UTC 2024 x86_64 User : www-data ( 33) PHP Version : 8.3.6 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : OFF Directory : /usr/share/doc/git/RelNotes/ |
Upload File : |
Git v1.7.5.1 Release Notes ========================== Fixes since v1.7.5 ------------------ * When an object "$tree:$path" does not exist, if $path does exist in the subtree of $tree that corresponds to the subdirectory the user is in, git now suggests using "$tree:./$path" in addition to the advice to use the full path from the root of the working tree. * The "--date=relative" output format used to say "X years, 12 months" when it should have said "X+1 years". * The smart-HTTP transfer was broken in 1.7.5 when the client needs to issue a small POST (which uses content-length) and then a large POST (which uses chunked) back to back. * "git clean" used to fail on an empty directory that is not readable, even though rmdir(2) could remove such a directory. Now we attempt it as the last resort. * The "--dirstat" option of "diff" family of commands used to totally ignore a change that only rearranged lines within a file. Such a change now counts as at least a minimum but non zero change. * The "--dirstat" option of "diff" family of commands used to use the pathname in the original, instead of the pathname in the result, when renames are involved. * "git pack-object" did not take core.bigfilethreashold into account (unlike fast-import); now it does. * "git reflog" ignored options like "--format=.." on the command line. * "git stash apply" used to refuse to work if there was any change in the working tree, even when the change did not overlap with the change the stash recorded. * "git stash apply @{99999}" was not diagnosed as an error, even when you did not have that many stash entries. * An error message from "git send-email" to diagnose a broken SMTP connection configuration lacked a space between "hello=<smtp-domain>" and "port=<smtp-server-port>". And other minor fixes and documentation updates.