{"thread":{"id":"28479","subject":"[ANNOUNCE] Git 1.7.6.4","startedAt":"2011-09-23T23:37:53Z","lastAt":"2011-09-24T10:35:04Z","messageCount":4,"participants":["Junio C Hamano","BJ Hargrave","Robin H. Johnson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"176111","messageId":"7vlitesucu.fsf@alter.siamese.dyndns.org","threadId":"28479","inReplyTo":null,"subject":"[ANNOUNCE] Git 1.7.6.4","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2011-09-23T23:37:53Z","receivedAt":"2011-09-23T23:37:53Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"The latest maintenance release Git 1.7.6.4 is available but not at the\nusual places.\n\nThe release tarballs are found at:\n\n    http://code.google.com/p/git-core/downloads/list\n\nand their SHA-1 checksums are:\n\ndf91e2c32d6097ab1c9d0edc56dd8cecb4e9b686  git-1.7.6.4.tar.gz\n6abd985e24b6585284cef7fae2e3046ba9201356  git-htmldocs-1.7.6.4.tar.gz\nc6f6d92f4005a7eccaf89e851c45768c18f7e65a  git-manpages-1.7.6.4.tar.gz\n\nAlso the following public repositories all have a copy of the v1.7.6.4\ntag and the maint branch that the tag points at:\n\n        url = git://repo.or.cz/alt-git.git\n        url = https://code.google.com/p/git-core/\n        url = git://git.sourceforge.jp/gitroot/git-core/git.git\n        url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core\n        url = https://github.com/gitster/git\n\n\nGit v1.7.6.4 Release Notes\n==========================\n\nFixes since v1.7.6.3\n--------------------\n\n * The error reporting logic of \"git am\" when the command is fed a file\n   whose mail-storage format is unknown was fixed.\n\n * \"git branch --set-upstream @{-1} foo\" did not expand @{-1} correctly.\n\n * \"git check-ref-format --print\" used to parrot a candidate string that\n   began with a slash (e.g. /refs/heads/master) without stripping it, to make\n   the result a suitably normalized string the caller can append to \"$GIT_DIR/\".\n\n * \"git clone\" failed to clone locally from a \".git\" file that itself\n   is not a directory but is a pointer to one.\n\n * \"git clone\" from a local repository that borrows from another\n   object store using a relative path in its objects/info/alternates\n   file did not adjust the alternates in the resulting repository.\n\n * \"git describe --dirty\" did not refresh the index before checking the\n   state of the working tree files.\n\n * \"git ls-files ../$path\" that is run from a subdirectory reported errors\n   incorrectly when there is no such path that matches the given pathspec.\n\n * \"git mergetool\" could loop forever prompting when nothing can be read\n   from the standard input.\n\nAlso contains minor fixes and documentation updates.\n"},{"id":"176115","messageId":"4850EB43-5CC7-4D33-90A8-1EDEE16ECAB7@bjhargrave.com","threadId":"28479","inReplyTo":"7vlitesucu.fsf@alter.siamese.dyndns.org","subject":"Re: [ANNOUNCE] Git 1.7.6.4","fromName":"BJ Hargrave","fromEmail":"bj@bjhargrave.com","sentAt":"2011-09-24T03:33:23Z","receivedAt":"2011-09-24T03:33:23Z","isPatch":false,"sender":{"key":"bj@bjhargrave.com","avatar":"https://gravatar.com/avatar/48e60c01177c0e8d3e60c996d54fbe36cf70058efcdd020375b4055e34fc05d7?d=mp&s=160"},"body":"On Sep 23, 2011, at 19:37 , Junio C Hamano wrote:\n> * \"git check-ref-format --print\" used to parrot a candidate string that\n>   began with a slash (e.g. /refs/heads/master) without stripping it, to make\n>   the result a suitably normalized string the caller can append to \"$GIT_DIR/\".\n\nWhen building 1.7.6.4 on my RHEL 4 system, it failed t1402-check-ref-format.sh:\n\n not ok - 19 ref name 'heads/foo' is not valid\n\nI bisected and found that commit f3738c1ce9193a4bf45ba1a3ea67d0cf32da0257 introduced the issue. \n\nThe test\n\n invalid_ref \"$(printf 'heads/foo\\177')\"\n\nwas added to t1402-check-ref-format.sh. However sh on my RHEL 4 system does not handle the DEL (\\177) character well in double quoted strings.\n\nsh-3.00$ echo $(printf 'hello\\177') | hexdump -C\n00000000  68 65 6c 6c 6f 7f 0a                              |hello..|\n00000007\nsh-3.00$ echo \"$(printf 'hello\\177')\" | hexdump -C\n00000000  68 65 6c 6c 6f 0a                                 |hello.|\n00000006\n\nThe double quotes cause the DEL (\\177) character to be discarded.\n\nCan this test be rewritten to avoid this apparent bug in sh on RHEL 4?\n\n-- \n\nBJ Hargrave\n"},{"id":"176116","messageId":"7vd3eqsinr.fsf@alter.siamese.dyndns.org","threadId":"28479","inReplyTo":"4850EB43-5CC7-4D33-90A8-1EDEE16ECAB7@bjhargrave.com","subject":"Re: [ANNOUNCE] Git 1.7.6.4","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2011-09-24T03:50:32Z","receivedAt":"2011-09-24T03:50:32Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"BJ Hargrave <bj@bjhargrave.com> writes:\n\n> The test\n>\n>  invalid_ref \"$(printf 'heads/foo\\177')\"\n>\n> was added to t1402-check-ref-format.sh. However sh on my RHEL 4 system\n> does not handle the DEL (\\177) character well in double quoted strings.\n>\n> sh-3.00$ echo $(printf 'hello\\177') | hexdump -C\n> 00000000  68 65 6c 6c 6f 7f 0a                              |hello..|\n> 00000007\n> sh-3.00$ echo \"$(printf 'hello\\177')\" | hexdump -C\n> 00000000  68 65 6c 6c 6f 0a                                 |hello.|\n> 00000006\n>\n> The double quotes cause the DEL (\\177) character to be discarded.\n>\n> Can this test be rewritten to avoid this apparent bug in sh on RHEL 4?\n\nFor older distros, I would prefer a workaround patch first tested by\ndistro packaging people and then upstreamed.\n\nThanks.\n"},{"id":"176123","messageId":"robbat2-20110924T103319-176337633Z@orbis-terrarum.net","threadId":"28479","inReplyTo":"7vlitesucu.fsf@alter.siamese.dyndns.org","subject":"Re: [ANNOUNCE] Git 1.7.6.4","fromName":"Robin H. Johnson","fromEmail":"robbat2@gentoo.org","sentAt":"2011-09-24T10:35:04Z","receivedAt":"2011-09-24T10:35:04Z","isPatch":false,"sender":{"key":"robbat2@gentoo.org","avatar":"https://avatars.githubusercontent.com/u/373898?v=4"},"body":"On Fri, Sep 23, 2011 at 04:37:53PM -0700,  Junio C Hamano wrote:\n> The latest maintenance release Git 1.7.6.4 is available but not at the\n> usual places.\n> \n> The release tarballs are found at:\n> \n>     http://code.google.com/p/git-core/downloads/list\n> \n> and their SHA-1 checksums are:\n> \n> df91e2c32d6097ab1c9d0edc56dd8cecb4e9b686  git-1.7.6.4.tar.gz\n> 6abd985e24b6585284cef7fae2e3046ba9201356  git-htmldocs-1.7.6.4.tar.gz\n> c6f6d92f4005a7eccaf89e851c45768c18f7e65a  git-manpages-1.7.6.4.tar.gz\nCan you please upload the manpages and htmldocs tarballs to\ncode.google.com downloads? We use them in packaging on Gentoo for users\nthat want the docs without all of the documentation build chain.\n\n(For 1.7.7.rc* too please).\n\n-- \nRobin Hugh Johnson\nGentoo Linux: Developer, Trustee & Infrastructure Lead\nE-Mail     : robbat2@gentoo.org\nGnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85\n"}]}