{"thread":{"id":"8622","subject":"[ANNOUNCE] GIT 1.5.2.2","startedAt":"2007-06-17T01:57:26Z","lastAt":"2007-07-12T20:57:39Z","messageCount":9,"participants":["Junio C Hamano","Arkadiusz Miskiewicz","Shawn O. Pearce","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"45201","messageId":"7vodjf1gxl.fsf@assigned-by-dhcp.pobox.com","threadId":"8622","inReplyTo":null,"subject":"[ANNOUNCE] GIT 1.5.2.2","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-06-17T01:57:26Z","receivedAt":"2007-06-17T01:57:26Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"The latest maintenance release GIT 1.5.2.2 is available at the\nusual places:\n\n http://www.kernel.org/pub/software/scm/git/\n\n git-1.5.2.2.tar.{gz,bz2}\t\t\t(tarball)\n git-htmldocs-1.5.2.2.tar.{gz,bz2}\t\t(preformatted docs)\n git-manpages-1.5.2.2.tar.{gz,bz2}\t\t(preformatted docs)\n RPMS/$arch/git-*-1.5.2.2-1.$arch.rpm\t(RPM)\n\nGIT v1.5.2.2 Release Notes\n==========================\n\nFixes since v1.5.2.1\n--------------------\n\n* Usability fix\n\n - git-gui is shipped with its updated blame interface. It is\n rumored that the older one was not just unusable but was\n active health hazard, but this one is actually pretty.\n Please see for yourself.\n\n* Bugfixes\n\n - \"git checkout fubar\" was utterly confused when there is a\n branch fubar and a tag fubar at the same time. It correctly\n checks out the branch fubar now.\n\n - \"git clone /path/foo\" to clone a local /path/foo.git\n repository left an incorrect configuration.\n\n - \"git send-email\" correctly unquotes RFC 2047 quoted names in\n the patch-email before using their values.\n\n - We did not accept number of seconds since epoch older than\n year 2000 as a valid timestamp. We now interpret positive\n integers more than 8 digits as such, which allows us to\n express timestamps more recent than March 1973.\n\n - git-cvsimport did not work when you have GIT_DIR to point\n your repository at a nonstandard location.\n\n - Some systems (notably, Solaris) lack hstrerror() to make\n h_errno human readable; prepare a replacement\n implementation.\n\n - .gitignore file listed git-core.spec but what we generate is\n git.spec, and nobody noticed for a long time.\n\n - \"git-merge-recursive\" does not try to run file level merge\n on binary files.\n\n - \"git-branch --track\" did not create tracking configuration\n correctly when the branch name had slash in it.\n\n - The email address of the user specified with user.email\n configuration was overriden by EMAIL environment variable.\n\n - The tree parser did not warn about tree entries with\n nonsense file modes, and assumed they must be blobs.\n\n - \"git log -z\" without any other request to generate diff still\n invoked the diff machinery, wasting cycles.\n\n* Documentation\n\n - Many updates to fix stale or missing documentation.\n\n - Although our documentation was primarily meant to be formatted\n with AsciiDoc7, formatting with AsciiDoc8 is supported better.\n\n\n----------------------------------------------------------------\n\nChanges since v1.5.2.1 are as follows:\n\nAlex Riesen (3):\n Make the installation target of git-gui a little less chatty\n Fix clone to setup the origin if its name ends with .git\n Add a local implementation of hstrerror for the system which do not have it\n\nGerrit Pape (1):\n Fix typo in remote branch example in git user manual\n\nJ. Bruce Fields (4):\n user-manual: quick-start updates\n user-manual: add a missing section ID\n Documentation: user-manual todo\n tutorial: use \"project history\" instead of \"changelog\" in header\n\nJakub Narebski (1):\n Generated spec file to be ignored is named git.spec and not git-core.spec\n\nJohannes Schindelin (2):\n Move buffer_is_binary() to xdiff-interface.h\n merge-recursive: refuse to merge binary files\n\nJohannes Sixt (1):\n Accept dates before 2000/01/01 when specified as seconds since the epoch\n\nJunio C Hamano (6):\n checkout: do not get confused with ambiguous tag/branch names\n $EMAIL is a last resort fallback, as it's system-wide.\n git-branch --track: fix tracking branch computation.\n Avoid diff cost on \"git log -z\"\n Documentation: adjust to AsciiDoc 8\n GIT 1.5.2.2\n\nKristian H淡gsberg (1):\n Unquote From line from patch before comparing with given from address.\n\nLuiz Fernando N. Capitulino (1):\n git-cherry: Document 'limit' command-line option\n\nMatthijs Melchior (1):\n New selection indication and softer colors\n\nMichael Milligan (1):\n git-cvsimport: Make sure to use $git_dir always instead of .git sometimes\n\nSam Vilain (2):\n fix documentation of unpack-objects -n\n Don't assume tree entries that are not dirs are blobs\n\nShawn O. Pearce (47):\n git-gui: Allow creating a branch when none exists\n git-gui: Allow as few as 0 lines of diff context\n git-gui: Don't quit when we destroy a child widget\n git-gui: Attach font_ui to all spinbox widgets\n git-gui: Verify Tcl/Tk is new enough for our needs\n Revert \"Make the installation target of git-gui a little less chatty\"\n git-gui: Add a 4 digit commit abbreviation to the blame viewer\n git-gui: Cleanup blame::new widget initialization\n git-gui: Remove empty blank line at end of blame\n git-gui: Improve the coloring in blame viewer\n git-gui: Simplify consecutive lines that come from the same commit\n git-gui: Use arror cursor in blame viewer file data\n git-gui: Display tooltips in blame viewer\n git-gui: Highlight the blame commit header from everything else\n git-gui: Remove unnecessary reshow of blamed commit\n git-gui: Cleanup minor style nit\n git-gui: Space the commit group continuation out in blame view\n git-gui: Show author initials in blame groups\n git-gui: Allow the user to control the blame/commit split point\n git-gui: Display a progress bar during blame annotation gathering\n git-gui: Allow digging through history in blame viewer\n git-gui: Combine blame groups only if commit and filename match\n git-gui: Show original filename in blame tooltip\n git-gui: Use a label instead of a button for the back button\n git-gui: Clip the commit summaries in the blame history menu\n git-gui: Remove the loaded column from the blame viewer\n git-gui: Remove unnecessary space between columns in blame viewer\n git-gui: Use lighter colors in blame view\n git-gui: Make the line number column slightly wider in blame\n git-gui: Automatically expand the line number column as needed\n git-gui: Remove unused commit_list from blame viewer\n git-gui: Better document our blame variables\n git-gui: Cleanup redundant column management in blame viewer\n git-gui: Switch internal blame structure to Tcl lists\n git-gui: Label the uncommitted blame history entry\n git-gui: Rename fields in blame viewer to better descriptions\n git-gui: Display the \"Loading annotation...\" message in italic\n git-gui: Run blame twice on the same file and display both outputs\n git-gui: Display both commits in our tooltips\n git-gui: Jump to original line in blame viewer\n git-gui: Use three colors for the blame viewer background\n git-gui: Improve our labeling of blame annotation types\n git-gui: Favor the original annotations over the recent ones\n git-gui: Changed blame header bar background to match main window\n git-gui: Include 'war on whitespace' fixes from git.git\n git-gui: Give amend precedence to HEAD over MERGE_MSG\n git-gui: Save geometry before the window layout is damaged\n\nwilliam pursell (1):\n Make command description imperative statement, not third-person present.\n"},{"id":"45220","messageId":"200706171230.37659.arekm@maven.pl","threadId":"8622","inReplyTo":"7vodjf1gxl.fsf@assigned-by-dhcp.pobox.com","subject":"Re: [ANNOUNCE] GIT 1.5.2.2","fromName":"Arkadiusz Miskiewicz","fromEmail":"arekm@maven.pl","sentAt":"2007-06-17T10:30:37Z","receivedAt":"2007-06-17T10:30:37Z","isPatch":false,"sender":{"key":"arekm@maven.pl","avatar":null},"body":"On Sunday 17 of June 2007, Junio C Hamano wrote:\n> The latest maintenance release GIT 1.5.2.2 is available at the\n> usual places:\n>\n> http://www.kernel.org/pub/software/scm/git/\n>\n> git-1.5.2.2.tar.{gz,bz2}\t\t\t(tarball)\n> git-htmldocs-1.5.2.2.tar.{gz,bz2}\t\t(preformatted docs)\n> git-manpages-1.5.2.2.tar.{gz,bz2}\t\t(preformatted docs)\n> RPMS/$arch/git-*-1.5.2.2-1.$arch.rpm\t(RPM)\n\nShould git testsuite (make test) go without any problem? (I'm asking because \nsome projects have test suites where some tests are expected to fail).\n\nI have 4 failures on amd64/linux and this git release:\n\n* FAIL 11: compare delta flavors\n\n perl -e '\n defined($_ = -s $_) or die for @ARGV;\n exit 1 if $ARGV[0] <= $ARGV[1];\n ' test-2-$packname_2.pack test-3-$packname_3.pack\n\n[...]\n\n* FAIL 16: corrupt a pack and see if verify catches\n cat test-1-${packname_1}.idx >test-3.idx &&\n cat test-2-${packname_2}.pack >test-3.pack &&\n if git-verify-pack test-3.idx\n then false\n else :;\n fi &&\n\n : PACK_SIGNATURE &&\n cat test-1-${packname_1}.pack >test-3.pack &&\n dd if=/dev/zero of=test-3.pack count=1 bs=1 conv=notrunc seek=2 \n&&\n if git-verify-pack test-3.idx\n then false\n else :;\n fi &&\n\n : PACK_VERSION &&\n cat test-1-${packname_1}.pack >test-3.pack &&\n dd if=/dev/zero of=test-3.pack count=1 bs=1 conv=notrunc seek=7 \n&&\n if git-verify-pack test-3.idx\n then false\n else :;\n fi &&\n\n : TYPE/SIZE byte of the first packed object data &&\n cat test-1-${packname_1}.pack >test-3.pack &&\n dd if=/dev/zero of=test-3.pack count=1 bs=1 conv=notrunc seek=12 \n&&\n if git-verify-pack test-3.idx\n then false\n else :;\n fi &&\n\n : sum of the index file itself &&\n l=`wc -c test-3.pack &&\n dd if=/dev/zero of=test-3.idx count=20 bs=1 conv=notrunc seek=$l \n&&\n if git-verify-pack test-3.pack\n then false\n else :;\n fi &&\n\n :\n\n[...]\n\n* FAIL 18: fake a SHA1 hash collision\n test -f .git/objects/c8/2de19312b6c3695c0c18f70709a6c535682a67 &&\n cp -f .git/objects/9d/235ed07cd19811a6ceb342de82f190e49c9f68 \n\\\n .git/objects/c8/2de19312b6c3695c0c18f70709a6c535682a67\n* FAIL 19: make sure index-pack detects the SHA1 collision\n git-index-pack -o bad.idx test-3.pack\n* failed 4 among 19 test(s)\n\n\n-- \nArkadiusz Miśkiewicz PLD/Linux Team\narekm / maven.pl http://ftp.pld-linux.org/\n"},{"id":"45250","messageId":"20070618032748.GH18491@spearce.org","threadId":"8622","inReplyTo":"7vodjf1gxl.fsf@assigned-by-dhcp.pobox.com","subject":"Re: [ANNOUNCE] GIT 1.5.2.2","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-06-18T03:27:48Z","receivedAt":"2007-06-18T03:27:48Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Junio C Hamano wrote:\n> GIT v1.5.2.2 Release Notes\n> ==========================\n> \n> Fixes since v1.5.2.1\n> --------------------\n> \n> * Usability fix\n> \n> - git-gui is shipped with its updated blame interface. It is\n> rumored that the older one was not just unusable but was\n> active health hazard, but this one is actually pretty.\n> Please see for yourself.\n\nUsability fix? More like finally implemented! _Now_ we can start\nto work on improving its usability. ;-)\n\n-- \nShawn.\n"},{"id":"45251","messageId":"20070618034322.GI18491@spearce.org","threadId":"8622","inReplyTo":"200706171230.37659.arekm@maven.pl","subject":"Re: [ANNOUNCE] GIT 1.5.2.2","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-06-18T03:43:23Z","receivedAt":"2007-06-18T03:43:23Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Arkadiusz Miskiewicz wrote:\n> On Sunday 17 of June 2007, Junio C Hamano wrote:\n> > The latest maintenance release GIT 1.5.2.2 is available at the\n> > usual places:\n> >\n> > http://www.kernel.org/pub/software/scm/git/\n> >\n> > git-1.5.2.2.tar.{gz,bz2}\t\t\t(tarball)\n> > git-htmldocs-1.5.2.2.tar.{gz,bz2}\t\t(preformatted docs)\n> > git-manpages-1.5.2.2.tar.{gz,bz2}\t\t(preformatted docs)\n> > RPMS/$arch/git-*-1.5.2.2-1.$arch.rpm\t(RPM)\n> \n> Should git testsuite (make test) go without any problem? (I'm asking because \n> some projects have test suites where some tests are expected to fail).\n\nNo, our test suite should always pass. Junio does not ship a release\nof Git where the test suite fails on his standard systems. We have\na lot of users running the current `master` and `next` branches on\na lot of different platforms, so usually platform specific breakages\nare caught relatively early, before a release gets made.\n\nWe do have tests we expect to fail, but then the test suite has an\ninversion in it. That is the test only passes if the underlying\noperation failed. ;-)\n\n> I have 4 failures on amd64/linux and this git release:\n...\n> * FAIL 16: corrupt a pack and see if verify catches\n> cat test-1-${packname_1}.idx >test-3.idx &&\n> cat test-2-${packname_2}.pack >test-3.pack &&\n\nHmm. That is t5300-pack-objects.sh. Something is really fishy\nif that test failed. We destroy a packfile and then look to see\nif the SHA-1 hash detects the change. It always does. So uh,\nwhat's up with your hardware that it doesn't fail?\n\nI just built 1.5.2.2 on one of my Gentoo Linux amd64 systems and I'm\nnot seeing any failures from the test suite. Not that I expected\nto find any; Linux amd64 is popular enough that a number of people\nrun it.\n\n-- \nShawn.\n"},{"id":"45253","messageId":"200706180821.59582.arekm@maven.pl","threadId":"8622","inReplyTo":"20070618034322.GI18491@spearce.org","subject":"Re: [ANNOUNCE] GIT 1.5.2.2","fromName":"Arkadiusz Miskiewicz","fromEmail":"arekm@maven.pl","sentAt":"2007-06-18T06:21:59Z","receivedAt":"2007-06-18T06:21:59Z","isPatch":false,"sender":{"key":"arekm@maven.pl","avatar":null},"body":"On Monday 18 of June 2007, Shawn O. Pearce wrote:\n> Arkadiusz Miskiewicz wrote:\n> > On Sunday 17 of June 2007, Junio C Hamano wrote:\n> > > The latest maintenance release GIT 1.5.2.2 is available at the\n> > > usual places:\n\n[...]\n\n> > Should git testsuite (make test) go without any problem? (I'm asking\n> > because some projects have test suites where some tests are expected to\n> > fail).\n>\n[...] \n\n>\n> > * FAIL 16: corrupt a pack and see if verify catches\n> > cat test-1-${packname_1}.idx >test-3.idx &&\n> > cat test-2-${packname_2}.pack >test-3.pack &&\n>\n> Hmm. That is t5300-pack-objects.sh. Something is really fishy\n> if that test failed. We destroy a packfile and then look to see\n> if the SHA-1 hash detects the change. It always does. So uh,\n> what's up with your hardware that it doesn't fail?\n\nThere is no problems known with this hardware (kernel builds are frequently \ndone on it and no problem occured so far). Test suite fails in the same place \neach time I'm running it.\n\n> I just built 1.5.2.2 on one of my Gentoo Linux amd64 systems and I'm\n> not seeing any failures from the test suite. Not that I expected\n> to find any; Linux amd64 is popular enough that a number of people\n> run it.\n\nNot all have the same enviroment. \n\ncoreutils-6.9-2.x86_64\ncurl-7.16.2-1.x86_64\ndiffutils-2.8.7-4.x86_64\nexpat-2.0.0-3.x86_64\nfindutils-4.2.31-1.x86_64\ngcc-4.2.0-6.x86_64\nglibc-2.6-1.i686\nglibc-2.6-1.x86_64\ngrep-2.5.1a-2.x86_64\nopenssl-0.9.8e-4.x86_64\nperl-5.8.8-11.x86_64\npython-2.5.1-2.x86_64\nsed-4.1.5-2.x86_64\nzlib-1.2.3-4.x86_64\n\n\nIf anyone is interested in debugging that problem then I can give ssh access \nto this machine.\n\n-- \nArkadiusz Miśkiewicz PLD/Linux Team\narekm / maven.pl http://ftp.pld-linux.org/\n"},{"id":"45255","messageId":"20070618062902.GL18491@spearce.org","threadId":"8622","inReplyTo":"200706180821.59582.arekm@maven.pl","subject":"Re: [ANNOUNCE] GIT 1.5.2.2","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-06-18T06:29:02Z","receivedAt":"2007-06-18T06:29:02Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Arkadiusz Miskiewicz wrote:\n> On Monday 18 of June 2007, Shawn O. Pearce wrote:\n> > Arkadiusz Miskiewicz wrote:\n> > > * FAIL 16: corrupt a pack and see if verify catches\n> > > cat test-1-${packname_1}.idx >test-3.idx &&\n> > > cat test-2-${packname_2}.pack >test-3.pack &&\n> >\n> > Hmm. That is t5300-pack-objects.sh.\n> \n> If anyone is interested in debugging that problem then I can give ssh access \n> to this machine.\n\nHow about we start with the output of:\n\n cd t && ./t5300-pack-objects.sh -v\n\n? That should be a lot more verbose, as it will include the\ncommands we are running and their stdout/stderr. Sometimes fun\ndetails about broken tools can be easily obtained from that output.\n\n-- \nShawn.\n"},{"id":"45256","messageId":"200706180835.57344.arekm@maven.pl","threadId":"8622","inReplyTo":"20070618062902.GL18491@spearce.org","subject":"Re: [ANNOUNCE] GIT 1.5.2.2","fromName":"Arkadiusz Miskiewicz","fromEmail":"arekm@maven.pl","sentAt":"2007-06-18T06:35:57Z","receivedAt":"2007-06-18T06:35:57Z","isPatch":false,"sender":{"key":"arekm@maven.pl","avatar":null},"body":"On Monday 18 of June 2007, Shawn O. Pearce wrote:\n> Arkadiusz Miskiewicz wrote:\n> > On Monday 18 of June 2007, Shawn O. Pearce wrote:\n> > > Arkadiusz Miskiewicz wrote:\n> > > > * FAIL 16: corrupt a pack and see if verify catches\n> > > > cat test-1-${packname_1}.idx >test-3.idx &&\n> > > > cat test-2-${packname_2}.pack >test-3.pack &&\n> > >\n> > > Hmm. That is t5300-pack-objects.sh.\n> >\n> > If anyone is interested in debugging that problem then I can give ssh\n> > access to this machine.\n>\n> How about we start with the output of:\n>\n> cd t && ./t5300-pack-objects.sh -v\n>\n> ? That should be a lot more verbose, as it will include the\n> commands we are running and their stdout/stderr. Sometimes fun\n> details about broken tools can be easily obtained from that output.\n\nThe reason was... missing /dev/zero! :-) Mystery solved, thanks!\n\n-- \nArkadiusz Miśkiewicz PLD/Linux Team\narekm / maven.pl http://ftp.pld-linux.org/\n"},{"id":"45419","messageId":"f5aori$sj7$1@sea.gmane.org","threadId":"8622","inReplyTo":"7vodjf1gxl.fsf@assigned-by-dhcp.pobox.com","subject":"Re: [ANNOUNCE] GIT 1.5.2.2","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2007-06-20T08:34:57Z","receivedAt":"2007-06-20T08:34:57Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Junio C Hamano wrote:\n\n>   - git-gui is shipped with its updated blame interface.  It is\n>     rumored that the older one was not just unusable but was\n>     active health hazard, but this one is actually pretty.\n>     Please see for yourself.\n\nI like the new interface very much, especially the info about who\nmade the change, and who moved the change to present place.\n\nIt would be nice though to have git-gui(1) man page describing 'blame'\nsubcommand of git-gui,, or have \"git blame --gui\" invoke \"git gui blame\".\ngitk has it's manpage, why not git-gui? AFAICT there is currently no way to\ndiscover this wonderfull tool given only manpages and git-gui help.\n\nPerhaps file browser in git-gui should have \"Blame\"/\"Annotate\" button?\n\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n"},{"id":"47205","messageId":"7v7ip5tk58.fsf@assigned-by-dhcp.cox.net","threadId":"8622","inReplyTo":"7vodjf1gxl.fsf@assigned-by-dhcp.pobox.com","subject":"[ANNOUNCE] GIT 1.5.2.4","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-07-12T20:57:39Z","receivedAt":"2007-07-12T20:57:39Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"The latest maintenance release GIT 1.5.2.4 is available at the\nusual places:\n\n http://www.kernel.org/pub/software/scm/git/\n\n git-1.5.2.4.tar.{gz,bz2}\t\t\t(tarball)\n git-htmldocs-1.5.2.4.tar.{gz,bz2}\t\t(preformatted docs)\n git-manpages-1.5.2.4.tar.{gz,bz2}\t\t(preformatted docs)\n RPMS/$arch/git-*-1.5.2.4-1.$arch.rpm\t(RPM)\n\n----------------------------------------------------------------\n\nGIT v1.5.2.4 Release Notes\n==========================\n\nFixes since v1.5.2.3\n--------------------\n\n * Bugfixes\n\n - \"git-gui\" bugfixes, including a handful fixes to run it\n better on Cygwin/MSYS.\n\n - \"git checkout\" failed to switch back and forth between\n branches, one of which has \"frotz -> xyzzy\" symlink and\n file \"xyzzy/filfre\", while the other one has a file\n \"frotz/filfre\".\n\n - \"git prune\" used to segfault upon seeing a commit that is\n referred to by a tree object (aka \"subproject\").\n\n - \"git diff --name-status --no-index\" mishandled an added file.\n\n - \"git apply --reverse --whitespace=warn\" still complained\n about whitespaces that a forward application would have\n introduced.\n\n * Documentation Fixes and Updates\n\n - A handful documentation updates.\n\n----------------------------------------------------------------\n\nChanges since v1.5.2.3 are as follows:\n\nAndy Parkins (2):\n Make git-prune submodule aware (and fix a SEGFAULT in the process)\n user-manual: grammar and style fixes\n\nGerrit Pape (1):\n git-gui: properly popup error if gitk should be started but is not installed\n\nJ. Bruce Fields (2):\n tutorial: Fix typo\n user-manual: more explanation of push and pull usage\n\nJim Meyering (1):\n Don't smash stack when $GIT_ALTERNATE_OBJECT_DIRECTORIES is too long\n\nJohannes Schindelin (3):\n diff --no-index: fix --name-status with added files\n glossary: add 'reflog'\n Fix \"apply --reverse\" with regard to whitespace\n\nJunio C Hamano (2):\n Teach read-tree 2-way merge to ignore intermediate symlinks\n GIT 1.5.2.4\n\nMichael Hendricks (1):\n Correctly document the name of the global excludes file configuration\n\nMiklos Vajna (1):\n Document - for git-format-patch\n\nShawn O. Pearce (10):\n git-gui: Unlock the index when cancelling merge dialog\n git-gui: Don't bind F5/M1-R in all windows\n git-gui: Bind M1-P to push action\n git-gui: Include a Push action on the left toolbar\n git-gui: Ensure windows shortcuts always have .bat extension\n git-gui: Skip nicknames when selecting author initials\n git-gui: Correct ls-tree buffering problem in browser\n git-gui: Don't linewrap within console windows\n Clarify documentation of fast-import's D subcommand\n git-gui: Work around bad interaction between Tcl and cmd.exe on ^{tree}\n\nWilliam Pursell (1):\n user-manual: fix directory name in git-archive example\n"}]}