{"thread":{"id":"29904","subject":"What's cooking in git.git (Mar 2012, #04; Fri, 9)","startedAt":"2012-03-10T01:35:46Z","lastAt":"2012-03-11T09:25:18Z","messageCount":2,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"186606","messageId":"7vboo52q6l.fsf@alter.siamese.dyndns.org","threadId":"29904","inReplyTo":null,"subject":"What's cooking in git.git (Mar 2012, #04; Fri, 9)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-03-10T01:35:46Z","receivedAt":"2012-03-10T01:35:46Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Here are the topics that have been cooking.  Commits prefixed with '-' are\nonly in 'pu' (proposed updates) while commits prefixed with '+' are in 'next'.\n\nTrivially correct fixes to old bugs may still graduate to 'master',\nbut otherwise we are mostly in \"regression fixes only\" mode until\n1.7.10 final (see http://tinyurl.com/gitCal for schedule).\n\nYou can find the changes described here in the integration branches of the\nrepositories listed at\n\n    http://git-blame.blogspot.com/p/git-public-repositories.html\n\n--------------------------------------------------\n[New Topics]\n\n* rs/unpack-trees-leakfix (2012-03-06) 1 commit\n  (merged to 'next' on 2012-03-07 at 69a69cd)\n + unpack-trees: plug minor memory leak\n\n* jh/apply-free-patch (2012-03-07) 1 commit\n - apply: do not leak patches and fragments\n\n* az/verify-tag-use-gpg-config (2012-03-08) 1 commit\n  (merged to 'next' on 2012-03-09 at d9e556f)\n + verify-tag: Parse GPG configuration options.\n\n\"git tag -s\" honored \"gpg.program\" configuration variable since\n1.7.9, but \"git tag -v\" and \"git verify-tag\" didn't.\n\nThis is a fairly low impact fix, and we may want to have it in\n1.7.10.\n\n* tb/maint-remove-irrelevant-i18n-test (2012-03-06) 1 commit\n  (merged to 'next' on 2012-03-07 at 23f2dd1)\n + t0204: remove a test that checks undefined behaviour\n\nI tentatively parked this in 'next' but later reverted the merge.\n\n* jc/maint-undefined-i18n-observation-test (2012-03-09) 1 commit\n - t0204: clarify the \"observe undefined behaviour\" test\n\nIt was unclear what a test in t0204 wanted to check; it turns out\nthat it was only to observe an undefined behaviour of the system,\nand did not anticipate one kind of reasonable error behaviour.\n\nReplaces the tb/maint-remove-irrelevant-i18n-test topic.\n\n* mm/push-default-switch-warning (2012-03-09) 1 commit\n - push: start warning upcoming default change for push.default\n\nThis resurrects an ancient patch I wrote during a discussion we had\nin the 1.6.3-1.6.4 era.  It also conflicts with the long-stalled\njc/advise-push-default topic and for a good reason.  The latter is a\nlower impact patch that uses a more focused approach to limit the\nscope to the target audience that actually needs help.\n\n* ph/rerere-doc (2012-03-08) 1 commit\n - rerere: Document 'rerere remaining'\n\n* sl/customize-sane-tool-path (2012-03-09) 1 commit\n - configure: allow user to prevent $PATH \"sanitization\" on Solaris\n\nWould be nice to hear from people who actually use autoconf, either\non Solaris or other platforms.\n\n--------------------------------------------------\n[Graduated to \"master\"]\n\n* cn/pull-rebase-message (2012-03-04) 1 commit\n  (merged to 'next' on 2012-03-04 at 5a6cd58)\n + Make git-{pull,rebase} message without tracking information friendlier\n\nThe advise message given when the user didn't give enough clue on what\nto merge was overly long.\n\n* jc/maint-diff-patch-header (2012-03-01) 3 commits\n  (merged to 'next' on 2012-03-02 at 2cd2059)\n + diff -p: squelch \"diff --git\" header for stat-dirty paths\n + t4011: illustrate \"diff-index -p\" on stat-dirty paths\n + t4011: modernise style\n (this branch is used by jc/diff-ignore-mode.)\n\n\"diff-index\" and friends showed \"diff --git\" header and nothing else\nfor a path that is only stat-dirty.\n\n* jc/pickaxe-ignore-case (2012-03-04) 3 commits\n  (merged to 'next' on 2012-03-04 at 1ad3a39)\n + ctype.c: Fix a sparse warning\n  (merged to 'next' on 2012-03-02 at 73a632b)\n + pickaxe: allow -i to search in patch case-insensitively\n + grep: use static trans-case table\n\n\"git log -G/-S\" pays attention to the \"-i\" option.\n\n* jh/threadable-symlink-check (2012-03-02) 1 commit\n  (merged to 'next' on 2012-03-05 at fdd667c)\n + Add threaded versions of functions in symlinks.c.\n\nIt probably is \"threadble\" not \"threaded\" but in any case this\nshould not regress the current callers.\n\n* jl/maint-submodule-relative (2012-03-04) 4 commits\n  (merged to 'next' on 2012-03-07 at e020e5c)\n + submodules: fix ambiguous absolute paths under Windows\n + submodules: refactor computation of relative gitdir path\n + submodules: always use a relative path from gitdir to work tree\n + submodules: always use a relative path to gitdir\n\nThe whole directory that houses a top-level superproject managed by\n\"git submodule\" can be moved to another place.\n\n* jn/maint-do-not-match-with-unsanitized-searchtext (2012-03-06) 1 commit\n  (merged to 'next' on 2012-03-06 at 768ce21)\n + gitweb: Fix fixed string (non-regexp) project search\n\n\"gitweb\" did use quotemeta() to prepare search string when asked to\ndo a fixed-string project search, but did not use it by mistake and\nused the user-supplied string instead.\n\n* kb/maint-prune-rmdir-closedir (2012-03-07) 1 commit\n  (merged to 'next' on 2012-03-07 at 2438c9a)\n + fix deletion of .git/objects sub-directories in git-prune/repack\n\nCall closedir() that iterates over a directory before rmdir() it.\n\n* nl/http-proxy-auth (2012-03-02) 1 commit\n  (merged to 'next' on 2012-03-04 at f368669)\n + http: support proxies that require authentication\n (this branch is used by nl/http-proxy-more.)\n\nAllow curl-based transport to use proxies that require authentication.\n\n* sl/modern-t0000 (2012-03-02) 1 commit\n  (merged to 'next' on 2012-03-04 at 2cd1508)\n + t0000: modernise style\n\n* th/mergetools-deltawalker (2012-03-05) 1 commit\n  (merged to 'next' on 2012-03-05 at 167c74f)\n + mergetools: add a plug-in to support DeltaWalker\n\nAdd plug-in to support DeltaWalker in difftool/mergetool.  \n\n* tr/maint-bundle-boundary (2012-03-01) 3 commits\n  (merged to 'next' on 2012-03-02 at c25692f)\n + bundle: keep around names passed to add_pending_object()\n + t5510: ensure we stay in the toplevel test dir\n + t5510: refactor bundle->pack conversion\n\n\"git bundle\" did not record boundary commits correctly when there\nare many of them.\n\n* vr/branch-doc (2012-03-06) 3 commits\n  (merged to 'next' on 2012-03-06 at 6be3587)\n + Documentation/git-branch: add default for --contains\n + Documentation/git-branch: fix a typo\n + Documentation/git-branch: cleanups\n\nDocumentation update.\n\n* zj/diff-stat-dyncol (2012-03-01) 10 commits\n  (merged to 'next' on 2012-03-01 at 79b4152)\n + diff --stat: add config option to limit graph width\n + diff --stat: enable limiting of the graph part\n + diff --stat: add a test for output with COLUMNS=40\n + diff --stat: use a maximum of 5/8 for the filename part\n + merge --stat: use the full terminal width\n + log --stat: use the full terminal width\n + show --stat: use the full terminal width\n + diff --stat: use the full terminal width\n + diff --stat: tests for long filenames and big change counts\n + Merge branches zj/decimal-width, zj/term-columns and jc/diff-stat-scaler\n\nRerolled again and looking good.\n\n--------------------------------------------------\n[Stalled]\n\n* dg/test-from-elsewhere (2012-03-04) 2 commits\n - Support out-of-tree Valgrind tests\n - Allow overriding GIT_BUILD_DIR\n\nBetter support for out-of-tree test scripts, but it appears that the\napproach needs to be rethought.  By repointing TEST_DIRECTORY to a\ndirectory other than $(pwd)/.., an out of place test script can reach\ntest helpers and freshly built Git relative to it (GIT_BUILD_DIR is\na mere short-hand for $TEST_DIRECTORY/..).\n\n* nd/optim-connected (2012-02-29) 1 commit\n - Perform cheaper connectivity check when pack is used as medium\n\nCheats the local connectivity check performed by \"git fetch\"\nslightly to gain some performance. This is a bit iffy.\n\n* nd/columns (2012-02-28) 10 commits\n - tag: add --column\n - column: support piping stdout to external git-column process\n - status: add --column\n - branch: add --column\n - help: reuse print_columns() for help -a\n - column: add column.ui for default column output settings\n - column: add dense layout support\n - column: add columnar layout\n - Stop starting pager recursively\n - Add git-column for columnar display\n\nRerolled; the configuration handling looked iffy, but otherwise well\nexplained.\n\n* hv/submodule-recurse-push (2012-02-13) 3 commits\n - push: teach --recurse-submodules the on-demand option\n - Refactor submodule push check to use string list instead of integer\n - Teach revision walking machinery to walk multiple times sequencially\n\nThe bottom one was not clearly explained and needs a reroll.\n\n* jc/advise-push-default (2011-12-18) 1 commit\n - push: hint to use push.default=upstream when appropriate\n\nPeff had a good suggestion outlining an updated code structure so\nthat somebody new can try to dip his or her toes in the development.\nAny takers?\n\n* jh/trace-use-startup-info (2012-03-02) 1 commit\n - Use startup_info->prefix rather than prefix.\n\nI tend to agree with the doubt of the author of this patch expressed.\n\n* ss/git-svn-prompt-sans-terminal (2012-01-04) 3 commits\n - fixup! 15eaaf4\n - git-svn, perl/Git.pm: extend Git::prompt helper for querying users\n - perl/Git.pm: \"prompt\" helper to honor GIT_ASKPASS and SSH_ASKPASS\n\nThe bottom one has been replaced with a rewrite based on comments\nfrom Ævar. The second one needs more work, both in perl/Git.pm and\nprompt.c, to give precedence to tty over SSH_ASKPASS when terminal\nis available.\n\n* jc/split-blob (2012-02-23) 7 commits\n - fixup?\n - chunked-object: streaming checkout\n - chunked-object: fallback checkout codepaths\n - bulk-checkin: support chunked-object encoding\n - bulk-checkin: allow the same data to be multiply hashed\n - new representation types in the packstream\n - varint-in-pack: refactor varint encoding/decoding\n\nNot ready.\n\nI finished the streaming checkout codepath, but as explained in\n127b177 (bulk-checkin: support chunked-object encoding, 2011-11-30),\nthese are still early steps of a long and painful journey. At least\npack-objects and fsck need to learn the new encoding for the series\nto be usable locally, and then index-pack/unpack-objects needs to\nlearn it to be used remotely.\n\nGiven that I heard a lot of noise that people want large files, and\nthat I was asked by somebody at GitTogether'11 privately for an\nadvice on how to pay developers (not me) to help adding necessary\nsupport, I am somewhat dissapointed that the original patch series\nthat was sent almost two months ago still remains here without much\ncomments and updates from the developer community. I even made the\ninterface to the logic that decides where to split chunks easily\nreplaceable, and I deliberately made the logic in the original patch\nextremely stupid to entice others, especially the \"bup\" fanboys, to\ncome up with a better logic, thinking that giving people an easy\ntarget to shoot for, they may be encouraged to help out. The plan is\nnot working :-(.\n\n--------------------------------------------------\n[Cooking]\n\n* jc/fmt-merge-msg-people (2012-03-08) 3 commits\n  (merged to 'next' on 2012-03-08 at be31aa9)\n + fmt-merge-msg.c: make util_as_int() return \"int\"\n  (merged to 'next' on 2012-03-07 at 76fbac3)\n + fmt-merge-msg: finishing touches\n  (merged to 'next' on 2012-03-05 at 38de349)\n + fmt-merge-msg: show those involved in a merged series\n\nThe \"fmt-merge-msg\" command learns to list the primary contributors\ninvolved in the side topic you are merging.\n\nJudging by the rate of \"oops, this is better\" fix-ups, it was good\nthat I decided to postpone this topic til the next cycle ;-)\n\n* nl/http-proxy-more (2012-03-05) 3 commits\n - http: handle proxy authentication failure (error 407)\n - http: handle proxy proactive authentication\n - http: try http_proxy env var when http.proxy config option is not set\n\nThe code to talk to http proxies learn to use the same credential\nAPI used to talk to the final http destinations.  It seems the\nre-rolling has stalled since the last review?\n\n* nd/stream-more (2012-03-07) 7 commits\n  (merged to 'next' on 2012-03-07 at 7325922)\n + update-server-info: respect core.bigfilethreshold\n + fsck: use streaming API for writing lost-found blobs\n + show: use streaming API for showing blobs\n + parse_object: avoid putting whole blob in core\n + cat-file: use streaming API to print blobs\n + Add more large blob test cases\n + streaming: make streaming-write-entry to be more reusable\n\nUse API to read blob data in smaller chunks in more places to\nreduce the memory footprint.\n\n* nd/threaded-index-pack (2012-03-02) 2 commits\n - index-pack: support multithreaded delta resolving\n - index-pack: split second pass obj handling into own function\n\nRerolled to fix a bug that was discovered with a trivial test, and\nresurrected from Stalled category, but I am reluctant to advance a\ntopic that can easily break many people's repositories at this late\nin the cycle.\n\nWhat is queued here is a couple of review cycles old; will discard\nand replace with a re-roll when it comes.\n\n--------------------------------------------------\n[Discarded]\n\n* jc/diff-ignore-case (2012-02-28) 6 commits\n . diff: -i is \"--ignore-case\" but means a bit more in \"log\"\n . diff: --ignore-case\n . xdiff: introduce XDF_IGNORE_CASE\n . xdiff: introduce XDF_INEXACT_MATCH\n . xdiff: PATIENCE/HISTOGRAM are not independent option bits\n . xdiff: remove XDL_PATCH_* macros\n\n* jc/diff-ignore-mode (2012-03-01) 1 commit\n . diff --ignore-mode-change\n"},{"id":"186642","messageId":"7vaa3nzdz5.fsf@alter.siamese.dyndns.org","threadId":"29904","inReplyTo":"7vboo52q6l.fsf@alter.siamese.dyndns.org","subject":"What's in \"What's cooking\"","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-03-11T09:25:18Z","receivedAt":"2012-03-11T09:25:18Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Here is a note to explain various sections and what the readers on\nthis list are expected to read from them in the periodic \"What's\ncooking\" summary.  This probably should be integrated in the\nperiodic \"A note from the maintainer\" posting eventually.\n\nThe first part is mostly a boilerplate message, but the second\nparagraph of it often explains where in the development cycle we\nare.  The last one (issue #4 of this month) said:\n\n   Trivially correct fixes to old bugs may still graduate to 'master',\n   but otherwise we are mostly in \"regression fixes only\" mode until\n   1.7.10 final (see http://tinyurl.com/gitCal for schedule).\n\nThe preamble is followed by various sections, each listing topics in\ndifferent \"doneness\".\n\nEach topic looks like this:\n\n  * cn/pull-rebase-message (2012-03-04) 1 commit\n    (merged to 'next' on 2012-03-04 at 5a6cd58)\n   + Make git-{pull,rebase} message without tracking information friendlier\n\n  The advise message given when the user didn't give enough clue on what\n  to merge was overly long.\n  Will merge to 'master'.\n\nA line that begins with a '*' has the name of a topic, the date of\nthe last activity on the topic and the number of changes in the\ntopic.  Then each commit on the topic is listed with prefix (\"+\",\n\"-\" or \".\").  The ones with \"+\" are already on 'next', and the dates\nwhen they were merged to 'next' also appear on this list. This will\ngive readers the rough idea of how long the topic has been cooking\nin 'next' (the branch active bug hunters and early adopters are\nexpected to be running) to measure the \"doneness\".\n\nThe list of commits on the topic is often followed by a few lines of\nfree-form text to summarize what the topic aims to achieve. This\noften goes literally to the draft release notes when the topic\ngraduates to 'master'.  Also I annotate my short-term plan for the\ntopic (\"Will merge to 'master' in the above example); it is very\nmuch appreciated if readers raise timely objections to this plan\n(e.g. \"Don't merge it yet, it is broken --- see that discussion\nthread\").\n\nThe [New topics] section lists topics that were not in my tree when\nthe previous issue of \"What's cooking\" was sent.\n\nThe [Graduated to \"master\"] section lists topics that have been\nmerged to 'master' since the previous issue. Even if you are not an\nactive bug hunter, please exercise the features/fixes these topics\nbrings to the system, as breakages or regressions caused by these\nwill appear in the next release if they are not noticed and fixed.\n\nThe [Stalled] section lists topics whose discussion has stalled, or\nre-rolled patches have not been seen for a while after the topic\nreceived review comments. This section is listed here so that people\ninterested in the topics in it can help the owners of them to move\nthings forward.\n\nThe [Cooking] section lists the remainder of the topics. They are\nmaking normal progress and are no cause for worries in general.\nThose whose commits are all in \"next\" are often just simmering to\ngive time to active bug hunters find unexpected problem in them.\nthose whose commits are not in \"next\" yet are still going through\nreview/revise cycle until they become ready.\n"}]}