{"push_id":1343784802,"size":31,"distinct_size":0,"ref":"refs/heads/jk/alternates-cleanup","head":"4598ada84a8c19c90a09f2d024c0df95c30e15ba","before":"6f621465d9ac45bfc22f005a6d05232dd5819fe2","commits":[{"sha":"f7e2e592cf9bad03bc3adc44dcbe498b876dc808","author":{"name":"Junio C Hamano","email":"3228067b6039a0d99bddaf967dafdecd5cc61600@pobox.com"},"message":"Merge branch 'dt/mailinfo' into maint\n\n* dt/mailinfo:\n  add David Turner's Two Sigma address","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/f7e2e592cf9bad03bc3adc44dcbe498b876dc808"},{"sha":"a813b19190a75e44b6ebd1ea5317ef5ed914cde0","author":{"name":"Junio C Hamano","email":"3228067b6039a0d99bddaf967dafdecd5cc61600@pobox.com"},"message":"Merge branch 'rs/copy-array' into maint\n\nCode cleanup.\n\n* rs/copy-array:\n  use COPY_ARRAY\n  add COPY_ARRAY","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/a813b19190a75e44b6ebd1ea5317ef5ed914cde0"},{"sha":"1f253d88face02b68a86fae36e6722c9ebc73856","author":{"name":"Junio C Hamano","email":"3228067b6039a0d99bddaf967dafdecd5cc61600@pobox.com"},"message":"Merge branch 'sg/ref-filter-parse-optim' into maint\n\nThe code that parses the format parameter of for-each-ref command\nhas seen a micro-optimization.\n\n* sg/ref-filter-parse-optim:\n  ref-filter: strip format option after a field name only once while parsing","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/1f253d88face02b68a86fae36e6722c9ebc73856"},{"sha":"18fd96f1d706357704c8d51f12b9412cd424ac49","author":{"name":"Junio C Hamano","email":"3228067b6039a0d99bddaf967dafdecd5cc61600@pobox.com"},"message":"Merge branch 'jk/graph-padding-fix' into maint\n\nThe \"graph\" API used in \"git log --graph\" miscounted the number of\noutput columns consumed so far when drawing a padding line, which\nhas been fixed; this did not affect any existing code as nobody\ntried to write anything after the padding on such a line, though.\n\n* jk/graph-padding-fix:\n  graph: fix extra spaces in graph_padding_line","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/18fd96f1d706357704c8d51f12b9412cd424ac49"},{"sha":"9534df98683e4268628619fb86af29e11e6db353","author":{"name":"Junio C Hamano","email":"3228067b6039a0d99bddaf967dafdecd5cc61600@pobox.com"},"message":"Merge branch 'jc/blame-abbrev' into maint\n\nAlmost everybody uses DEFAULT_ABBREV to refer to the default\nsetting for the abbreviation, but \"git blame\" peeked into\nunderlying variable bypassing the macro for no good reason.\n\n* jc/blame-abbrev:\n  blame: use DEFAULT_ABBREV macro","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/9534df98683e4268628619fb86af29e11e6db353"},{"sha":"54a9f14743748ada4bef3caffa45c6170ae4da32","author":{"name":"Junio C Hamano","email":"3228067b6039a0d99bddaf967dafdecd5cc61600@pobox.com"},"message":"Merge branch 'pb/rev-list-reverse-with-count' into maint\n\nDoc update to clarify what \"log -3 --reverse\" does.\n\n* pb/rev-list-reverse-with-count:\n  rev-list-options: clarify the usage of --reverse","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/54a9f14743748ada4bef3caffa45c6170ae4da32"},{"sha":"e1eb84cccb927834acae58ec2c0f727c7bf184c7","author":{"name":"Junio C Hamano","email":"3228067b6039a0d99bddaf967dafdecd5cc61600@pobox.com"},"message":"Merge branch 'kd/mailinfo-quoted-string' into maint\n\nAn author name, that spelled a backslash-quoted double quote in the\nhuman readable part \"My \\\"double quoted\\\" name\", was not unquoted\ncorrectly while applying a patch from a piece of e-mail.\n\n* kd/mailinfo-quoted-string:\n  mailinfo: unescape quoted-pair in header fields\n  t5100-mailinfo: replace common path prefix with variable","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/e1eb84cccb927834acae58ec2c0f727c7bf184c7"},{"sha":"0bc409dab941d7df065c486342cefcde78647c42","author":{"name":"Junio C Hamano","email":"3228067b6039a0d99bddaf967dafdecd5cc61600@pobox.com"},"message":"Merge branch 'rs/git-gui-use-modern-git-merge-syntax' into maint\n\nThe original command line syntax for \"git merge\", which was \"git\nmerge <msg> HEAD <parent>...\", has been deprecated for quite some\ntime, and \"git gui\" was the last in-tree user of the syntax.  This\nis finally fixed, so that we can move forward with the deprecation.\n\n* rs/git-gui-use-modern-git-merge-syntax:\n  git-gui: stop using deprecated merge syntax","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/0bc409dab941d7df065c486342cefcde78647c42"},{"sha":"f7f0a87e0a27a1baaf782af7cec18fd23fdf35de","author":{"name":"Junio C Hamano","email":"3228067b6039a0d99bddaf967dafdecd5cc61600@pobox.com"},"message":"Merge branch 'jc/verify-loose-object-header' into maint\n\nCodepaths that read from an on-disk loose object were too loose in\nvalidating what they are reading is a proper object file and\nsometimes read past the data they read from the disk, which has\nbeen corrected.  H/t to Gustavo Grieco for reporting.\n\n* jc/verify-loose-object-header:\n  unpack_sha1_header(): detect malformed object header\n  streaming: make sure to notice corrupt object","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/f7f0a87e0a27a1baaf782af7cec18fd23fdf35de"},{"sha":"fdb70b16a006f82b65fb92995886a074c829f587","author":{"name":"Junio C Hamano","email":"3228067b6039a0d99bddaf967dafdecd5cc61600@pobox.com"},"message":"Merge branch 'jc/worktree-config' into maint\n\n\"git worktree\", even though it used the default_abbrev setting that\nought to be affected by core.abbrev configuration variable, ignored\nthe variable setting.  The command has been taught to read the\ndefault set of configuration variables to correct this.\n\n* jc/worktree-config:\n  worktree: honor configuration variables","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/fdb70b16a006f82b65fb92995886a074c829f587"},{"sha":"6823506f364cd02589dd4485108516bd6bea8d9e","author":{"name":"Junio C Hamano","email":"3228067b6039a0d99bddaf967dafdecd5cc61600@pobox.com"},"message":"Merge branch 'jk/verify-packfile-gently' into maint\n\nA low-level function verify_packfile() was meant to show errors\nthat were detected without dying itself, but under some conditions\nit didn't and died instead, which has been fixed.\n\n* jk/verify-packfile-gently:\n  verify_packfile: check pack validity before accessing data","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/6823506f364cd02589dd4485108516bd6bea8d9e"},{"sha":"74eeaf7b72a94bd3e0ff275edb90e6ee2423b529","author":{"name":"Junio C Hamano","email":"3228067b6039a0d99bddaf967dafdecd5cc61600@pobox.com"},"message":"Start preparing for 2.10.2\n\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/74eeaf7b72a94bd3e0ff275edb90e6ee2423b529"},{"sha":"3cdd5d19178a54d2e51b5098d43b57571241d0ab","author":{"name":"Junio C Hamano","email":"3228067b6039a0d99bddaf967dafdecd5cc61600@pobox.com"},"message":"Sync with maint\n\n* maint:\n  Start preparing for 2.10.2","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/3cdd5d19178a54d2e51b5098d43b57571241d0ab"},{"sha":"f4a089b345d2a6012769e79d24395332a5ede9a9","author":{"name":"Jeff King","email":"7e57302763bea699aee296fb53304dc616ab92d5@peff.net"},"message":"t5613: drop reachable_via function\n\nThis function was never used since its inception in dd05ea1\n(test case for transitive info/alternates, 2006-05-07).\nWhich is just as well, since it mutates the repo state in a\nway that would invalidate further tests, without cleaning up\nafter itself. Let's get rid of it so that nobody is tempted\nto use it.","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/f4a089b345d2a6012769e79d24395332a5ede9a9"},{"sha":"c08843c109b9cab3f1fbb8f45046d07806abccf1","author":{"name":"Jeff King","email":"7e57302763bea699aee296fb53304dc616ab92d5@peff.net"},"message":"t5613: drop test_valid_repo function\n\nThis function makes sure that \"git fsck\" does not report any\nerrors. But \"--full\" has been the default since f29cd39\n(fsck: default to \"git fsck --full\", 2009-10-20), and we can\nuse the exit code (instead of counting the lines) since\ne2b4f63 (fsck: exit with non-zero status upon errors,\n2007-03-05).\n\nSo we can just use \"git fsck\", which is shorter and more\nflexible (e.g., we can use \"git -C\").","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/c08843c109b9cab3f1fbb8f45046d07806abccf1"},{"sha":"60ab007eeeab27feffed8ab1cb982b07819db15f","author":{"name":"Jeff King","email":"7e57302763bea699aee296fb53304dc616ab92d5@peff.net"},"message":"t5613: use test_must_fail\n\nBesides being our normal style, this correctly checks for an\nerror exit() versus signal death.","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/60ab007eeeab27feffed8ab1cb982b07819db15f"},{"sha":"6906fc5aa92453a8d6a443c3a68b061f827c4ea5","author":{"name":"Jeff King","email":"7e57302763bea699aee296fb53304dc616ab92d5@peff.net"},"message":"t5613: whitespace/style cleanups\n\nOur normal test style these days puts the opening quote of\nthe body on the description line, and indents the body with\na single tab. This ancient test did not follow this.","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/6906fc5aa92453a8d6a443c3a68b061f827c4ea5"},{"sha":"5041572ad585c6e1e3189e19008143c1fd990e63","author":{"name":"Jeff King","email":"7e57302763bea699aee296fb53304dc616ab92d5@peff.net"},"message":"t5613: do not chdir in main process\n\nOur usual style when working with subdirectories is to chdir\ninside a subshell or to use \"git -C\", which means we do not\nhave to constantly return to the main test directory. Let's\nconvert this old test, which does not follow that style.","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/5041572ad585c6e1e3189e19008143c1fd990e63"},{"sha":"9aac1ed861f84672e9f8225698f7af8b7c706306","author":{"name":"Jeff King","email":"7e57302763bea699aee296fb53304dc616ab92d5@peff.net"},"message":"t5613: clarify \"too deep\" recursion tests\n\nThese tests are just trying to show that we allow recursion\nup to a certain depth, but not past it. But the counting is\na bit non-intuitive, and rather than test at the edge of the\nbreakage, we test \"OK\" cases in the middle of the chain.\nLet's explain what's going on, and explicitly test the\nswitch between \"OK\" and \"too deep\".","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/9aac1ed861f84672e9f8225698f7af8b7c706306"},{"sha":"a6e470e85b8e8a44d6ae22cabfc51d8315f48044","author":{"name":"Jeff King","email":"7e57302763bea699aee296fb53304dc616ab92d5@peff.net"},"message":"link_alt_odb_entry: handle normalize_path errors\n\nWhen we add a new alternate to the list, we try to normalize\nout any redundant \"..\", etc. However, we do not look at the\nreturn value of normalize_path_copy(), and will happily\ncontinue with a path that could not be normalized. Worse,\nthe normalizing process is done in-place, so we are left\nwith whatever half-finished working state the normalizing\nfunction was in.\n\nFortunately, this cannot cause us to read past the end of\nour buffer, as that working state will always leave the\nNUL from the original path in place. And we do tend to\nnotice problems when we check is_directory() on the path.\nBut you can see the nonsense that we feed to is_directory\nwith an entry like:\n\n  this/../../is/../../way/../../too/../../deep/../../to/../../resolve\n\nin your objects/info/alternates, which yields:\n\n  error: object directory\n  /to/e/deep/too/way//ects/this/../../is/../../way/../../too/../../deep/../../to/../../resolve\n  does not exist; check .git/objects/info/alternates.\n\nWe can easily fix this just by checking the return value.\nBut that makes it hard to generate a good error message,\nsince we're normalizing in-place and our input value has\nbeen overwritten by cruft.\n\nInstead, let's provide a strbuf helper that does an in-place\nnormalize, but restores the original contents on error. This\nuses a second buffer under the hood, which is slightly less\nefficient, but this is not a performance-critical code path.\n\nThe strbuf helper can also properly set the \"len\" parameter\nof the strbuf before returning. Just doing:\n\n  normalize_path_copy(buf.buf, buf.buf);\n\nwill shorten the string, but leave buf.len at the original\nlength. That may be confusing to later code which uses the\nstrbuf.","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/a6e470e85b8e8a44d6ae22cabfc51d8315f48044"}]}
{"actor":{"display_login":"peff"}}