{"thread":{"id":"27256","subject":"[ANNOUNCE] Git 1.7.5.1","startedAt":"2011-05-05T01:35:46Z","lastAt":"2011-05-05T17:40:40Z","messageCount":3,"participants":["Junio C Hamano","Sverre Rabbelier","Piotr Krukowiecki"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"167060","messageId":"7vfwouc4jx.fsf@alter.siamese.dyndns.org","threadId":"27256","inReplyTo":null,"subject":"[ANNOUNCE] Git 1.7.5.1","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2011-05-05T01:35:46Z","receivedAt":"2011-05-05T01:35:46Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"The latest maintenance release Git 1.7.5.1 is available at the\nusual places:\n\n http://www.kernel.org/pub/software/scm/git/\n\n git-1.7.5.1.tar.{gz,bz2}\t\t\t(source tarball)\n git-htmldocs-1.7.5.1.tar.{gz,bz2}\t\t(preformatted docs)\n git-manpages-1.7.5.1.tar.{gz,bz2}\t\t(preformatted docs)\n\nThe RPM binary packages for a few architectures are found in:\n\n RPMS/$arch/git-*-1.7.5.1-1.fc13.$arch.rpm\t(RPM)\n\n\n\nGit v1.7.5.1 Release Notes\n==========================\n\nFixes since v1.7.5\n------------------\n\n * When an object \"$tree:$path\" does not exist, if $path does exist in the\n subtree of $tree that corresponds to the subdirectory the user is in,\n git now suggests using \"$tree:./$path\" in addition to the advice to use\n the full path from the root of the working tree.\n\n * The \"--date=relative\" output format used to say \"X years, 12 months\"\n when it should have said \"X+1 years\".\n\n * The smart-HTTP transfer was broken in 1.7.5 when the client needs\n to issue a small POST (which uses content-length) and then a large\n POST (which uses chunked) back to back.\n\n * \"git clean\" used to fail on an empty directory that is not readable,\n even though rmdir(2) could remove such a directory. Now we attempt it\n as the last resort.\n\n * The \"--dirstat\" option of \"diff\" family of commands used to totally\n ignore a change that only rearranged lines within a file. Such a\n change now counts as at least a minimum but non zero change.\n\n * The \"--dirstat\" option of \"diff\" family of commands used to use the\n pathname in the original, instead of the pathname in the result,\n when renames are involved.\n\n * \"git pack-object\" did not take core.bigfilethreashold into account\n (unlike fast-import); now it does.\n\n * \"git reflog\" ignored options like \"--format=..\" on the command line.\n\n * \"git stash apply\" used to refuse to work if there was any change in\n the working tree, even when the change did not overlap with the change\n the stash recorded.\n\n * \"git stash apply @{99999}\" was not diagnosed as an error, even when you\n did not have that many stash entries.\n\n * An error message from \"git send-email\" to diagnose a broken SMTP\n connection configuration lacked a space between \"hello=\"\n and \"port=\".\n\nAnd other minor fixes and documentation updates.\n\n----------------------------------------------------------------\n\nChanges since v1.7.5 are as follows:\n\nAlex Riesen (1):\n clean: unreadable directory may still be rmdir-able if it is empty\n\nDan McGee (2):\n stash: add two more tests for --no-keep-index\n stash: ensure --no-keep-index and --patch can be used in any order\n\nJeff King (3):\n stash: fix accidental apply of non-existent stashes\n stash: drop dirty worktree check on apply\n upload-pack: start pack-objects before async rev-list\n\nJohan Herland (4):\n --dirstat: Describe non-obvious differences relative to --stat or regular diff\n --dirstat-by-file: Make it faster and more correct\n Teach --dirstat not to completely ignore rearranged lines within a file\n --dirstat: In case of renames, use target filename instead of source filename\n\nJon Seymour (1):\n stash: fix false positive in the invalid ref test.\n\nJunio C Hamano (4):\n Teach core.bigfilethreashold to pack-objects\n http: clear POSTFIELDS when initializing a slot\n Start 1.7.5.1 maintenance track\n Git 1.7.5.1\n\nMichael J Gruber (6):\n builtin/log.c: separate default and setup of cmd_log_init()\n t/t1411: test reflog with formats\n reflog: fix overriding of command line options\n t1506: factor out test for \"Did you mean...\"\n sha1_name: Suggest commit:./file for path in subdir\n date: avoid \"X years, 12 months\" in relative dates\n\nSylvain Rabot (1):\n git-send-email: fix missing space in error message\n\nValentin Haenel (1):\n git-add.txt: document 'add.ignoreErrors'\n"},{"id":"167103","messageId":"BANLkTikV0-efkU+V90i=hPkMLYXi2Puw4w@mail.gmail.com","threadId":"27256","inReplyTo":"7vfwouc4jx.fsf@alter.siamese.dyndns.org","subject":"Re: [ANNOUNCE] Git 1.7.5.1","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2011-05-05T11:13:01Z","receivedAt":"2011-05-05T11:13:01Z","isPatch":false,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nOn Thu, May 5, 2011 at 03:35, Junio C Hamano wrote:\n>  * \"git stash apply\" used to refuse to work if there was any change in\n>   the working tree, even when the change did not overlap with the change\n>   the stash recorded.\n\nDoes this mean that I won't get the \"you have unstaged changes, please\nadd them\" message anymore for the non-overlapping case? If so, nice!\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"167134","messageId":"BANLkTi=7=gnirqkV=ygf_FOytdAT3L0iNA@mail.gmail.com","threadId":"27256","inReplyTo":"BANLkTikV0-efkU+V90i=hPkMLYXi2Puw4w@mail.gmail.com","subject":"Re: [ANNOUNCE] Git 1.7.5.1","fromName":"Piotr Krukowiecki","fromEmail":"piotr.krukowiecki@gmail.com","sentAt":"2011-05-05T17:40:40Z","receivedAt":"2011-05-05T17:40:40Z","isPatch":false,"sender":{"key":"piotr.krukowiecki@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3259959?v=4"},"body":"On Thu, May 5, 2011 at 1:13 PM, Sverre Rabbelier wrote:\n> Heya,\n>\n> On Thu, May 5, 2011 at 03:35, Junio C Hamano wrote:\n>>  * \"git stash apply\" used to refuse to work if there was any change in\n>>   the working tree, even when the change did not overlap with the change\n>>   the stash recorded.\n>\n> Does this mean that I won't get the \"you have unstaged changes, please\n> add them\" message anymore for the non-overlapping case? If so, nice!\n\nI think this also partially fixes problem with git-svn and concurrency described\nhere: http://article.gmane.org/gmane.comp.version-control.git/171481\n\ngit-svn now works correctly if during dcommit someone else made a change to\nsvn repository but the change did not touch dcommited file.\n\nIt still stops and looses history if change was in the same file.\n\nThanks,\n\n-- \nPiotr Krukowiecki\n"}]}