{"thread":{"id":"29671","subject":"What's cooking in git.git (Feb 2012, #07; Mon, 20)","startedAt":"2012-02-20T10:24:41Z","lastAt":"2012-02-20T10:24:41Z","messageCount":1,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"184981","messageId":"7vzkcdls46.fsf@alter.siamese.dyndns.org","threadId":"29671","inReplyTo":null,"subject":"What's cooking in git.git (Feb 2012, #07; Mon, 20)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-02-20T10:24:41Z","receivedAt":"2012-02-20T10:24:41Z","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\nThe first maintenance release v1.7.9.1 ironed out usability kinks in the\nnew features added in v1.7.9 release.  Topics that add new features and\nfixes that have been cooking in 'next' start to graduate to 'master'\nagain.\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[Graduated to \"master\"]\n\n* cb/maint-rev-list-verify-object (2012-02-13) 1 commit\n  (merged to 'next' on 2012-02-16 at a407b9a)\n + git rev-list: fix invalid typecast\n\nFixes an obscure bug in \"rev-list --verify\" that skipped verification\ndepending on the phase of the moon, which dates back to 1.7.8.x series.\n\n* cb/maint-t5541-make-server-port-portable (2012-02-13) 1 commit\n  (merged to 'next' on 2012-02-16 at 762eefb)\n + t5541: check error message against the real port number used\n\nTest fix.\n\n* cb/receive-pack-keep-errors (2012-02-13) 1 commit\n  (merged to 'next' on 2012-02-16 at 9ff846e)\n + do not override receive-pack errors\n\nSometimes error status detected by a check in an earlier phase of\nreceive-pack (the other end of 'git push') was lost by later checks,\nresulting in false indication of success.\n\n* cb/transfer-no-progress (2012-02-13) 1 commit\n  (merged to 'next' on 2012-02-16 at ff17092)\n + push/fetch/clone --no-progress suppresses progress output\n\nThe transport programs ignored --no-progress and showed progress when\nsending their output to a terminal.\n\n* jc/diff-stat-scaler (2012-02-14) 1 commit\n  (merged to 'next' on 2012-02-16 at 404d336)\n + diff --stat: show bars of same length for paths with same amount of changes\n\nThe output from \"git diff --stat\" for two paths that have the same amount\nof changes showed graph bars of different length due to the way we handled\nrounding errors.\n\n* tg/tag-points-at (2012-02-13) 2 commits\n  (merged to 'next' on 2012-02-13 at a8f4046)\n + builtin/tag.c: Fix a sparse warning\n  (merged to 'next' on 2012-02-10 at 4bff88f)\n + tag: add --points-at list option\n\n* zj/decimal-width (2012-02-14) 1 commit\n  (merged to 'next' on 2012-02-16 at 72805c4)\n + make lineno_width() from blame reusable for others\n (this branch is used by zj/diff-stat-dyncol.)\n\nRefactoring.\n\n* zj/term-columns (2012-02-13) 1 commit\n  (merged to 'next' on 2012-02-16 at fe70c88)\n + pager: find out the terminal width before spawning the pager\n (this branch is used by zj/diff-stat-dyncol.)\n\nFixes \"git -p cmd\" for any subcommand that cares about the true terminal\nwidth.\n\n--------------------------------------------------\n[New Topics]\n\n* fc/push-prune (2012-02-17) 2 commits\n - remote: reorganize check_pattern_match()\n - remote: use a local variable in match_push_refs()\n\nThe first two of the three-patch RFC series.  The second one and the third\none (not queued) both need better explanation, and the third one also had\na handful of minor yuck factors all of which should be straightforward to\nimprove.\n\nExpecting a reroll.\n\n* jc/add-refresh-unmerged (2012-02-17) 1 commit\n - refresh_index: do not show unmerged path that is outside pathspec\n\n\"git add --refresh <pathspec>\" warned about unmerged paths outside the\ngiven pathspec.\n\n* jc/diff-ignore-case (2012-02-19) 6 commits\n - diff -i\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\"git diff\" learned \"--ignore-case\" option.\n\n* jn/gitweb-hilite-regions (2012-02-19) 5 commits\n - gitweb: Use esc_html_match_hl() in 'grep' search\n - gitweb: Highlight matched part of shortened project description\n - gitweb: Highlight matched part of project description when searching projects\n - gitweb: Highlight matched part of project name when searching projects\n - gitweb: Introduce esc_html_hl_regions\n (this branch uses jn/gitweb-search-optim.)\n\nNot reviewed and do not know what this is about yet ;-).\n\n* jn/gitweb-search-optim (2012-02-19) 3 commits\n - gitweb: Faster project search\n - gitweb: Option for filling only specified info in fill_project_list_info\n - gitweb: Refactor checking if part of project info need filling\n (this branch is used by jn/gitweb-hilite-regions.)\n\nThe API introduced in the second step still has yucky design, but at least\nit is more clear than the previous rounds what this is trying to do.\n\n* js/configure-libintl (2012-02-20) 1 commit\n - configure: don't use -lintl when there is no gettext support\n\nBuild fix for autoconf, meant for 'maint' track.\n\n* pj/remote-set-branches-usage-fix (2012-02-19) 1 commit\n - remote: fix set-branches usage and documentation\n\nDocumentation fix.\n\n--------------------------------------------------\n[Stalled]\n\n* jl/maint-submodule-relative (2012-02-09) 2 commits\n - submodules: always use a relative path from gitdir to work tree\n - submodules: always use a relative path to gitdir\n\nThe second one looked iffy.\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* zj/diff-stat-dyncol (2012-02-15) 6 commits\n . diff --stat: use less columns for change counts\n - (squash to the previous -- replace the last line of the log with the following)\n - diff --stat: use the full terminal width\n - (squash to the previous -- replace the log message with this)\n - diff --stat: tests for long filenames and big change counts\n - Merge branches zj/decimal-width and zj/term-columns\n\nI am beginning to think that the last one should wait until the dust from\nthe earlier part settles.\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 that\nsomebody new can try to dip his or her toes in the development. Any\ntakers?\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 from\nÆvar. The second one needs more work, both in perl/Git.pm and prompt.c, to\ngive precedence to tty over SSH_ASKPASS when terminal is available.\n\n* jc/split-blob (2012-01-24) 6 commits\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 127b177\n(bulk-checkin: support chunked-object encoding, 2011-11-30), these are\nstill early steps of a long and painful journey. At least pack-objects and\nfsck need to learn the new encoding for the series to be usable locally,\nand then index-pack/unpack-objects needs to learn it to be used remotely.\n\nGiven that I heard a lot of noise that people want large files, and that I\nwas asked by somebody at GitTogether'11 privately for an advice on how to\npay developers (not me) to help adding necessary support, I am somewhat\ndissapointed that the original patch series that was sent almost two\nmonths ago still remains here without much comments and updates from the\ndeveloper community. I even made the interface to the logic that decides\nwhere to split chunks easily replaceable, and I deliberately made the\nlogic in the original patch extremely stupid to entice others, especially\nthe \"bup\" fanboys, to come up with a better logic, thinking that giving\npeople an easy target to shoot for, they may be encouraged to help\nout. The plan is not working :-(.\n\n* nd/columns (2012-02-08) 15 commits\n . column: Fix some compiler and sparse warnings\n . column: add a corner-case test to t3200\n . columns: minimum coding style fixes\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: support columns with different widths\n . column: add columnar layout\n . Stop starting pager recursively\n . Add git-column and column mode parsing\n . column: add API to print items in columns\n . Save terminal width before setting up pager\n\nExpecting a reroll on top of zj/term-columns topic.\n\n--------------------------------------------------\n[Cooking]\n\n* jk/diff-highlight (2012-02-13) 5 commits\n  (merged to 'next' on 2012-02-20 at ba040ae)\n + diff-highlight: document some non-optimal cases\n + diff-highlight: match multi-line hunks\n + diff-highlight: refactor to prepare for multi-line hunks\n + diff-highlight: don't highlight whole lines\n + diff-highlight: make perl strict and warnings fatal\n\nUpdates diff-highlight (in contrib/).\n\n* jn/gitweb-unborn-head (2012-02-17) 1 commit\n  (merged to 'next' on 2012-02-20 at 80e3ff2)\n + gitweb: Fix \"heads\" view when there is no current branch\n\n\"gitweb\" compared non-existent value of HEAD with the names of commit\nobjects at tips of branches, triggering runtime warnings.\n\n* tr/perftest (2012-02-17) 3 commits\n  (merged to 'next' on 2012-02-20 at 4c75ba9)\n + Add a performance test for git-grep\n + Introduce a performance testing framework\n + Move the user-facing test library to test-lib-functions.sh\n\n* jb/required-filter (2012-02-17) 1 commit\n . Add a setting to require a filter to be successful\n\nA content filter used to be a way to make the recorded contents \"more\nuseful\", but this defines a way to optionally mark a filter \"required\".\n\nA few test in t0021 use 'false' as the filter, which can exit without\nreading any byte from us, before we start writing and causes us to die\nwith SIGPIPE, leading to intermittent test failure.  I think treating this\nas a failure of running the filter (the end user's filter should read what\nis fed in full, produce its output and write the result back to us) is the\nright thing to do, so this patch needs update the surrounding code to\nhandle such a situation better, probably by using sigchain_push(SIGPIPE)\nor something.\n\n* jk/config-include (2012-02-17) 10 commits\n  (merged to 'next' on 2012-02-20 at 7b150b7)\n + config: add include directive\n + config: eliminate config_exclusive_filename\n + config: stop using config_exclusive_filename\n + config: provide a version of git_config with more options\n + config: teach git_config_rename_section a file argument\n + config: teach git_config_set_multivar_in_file a default path\n + config: copy the return value of prefix_filename\n + t1300: add missing &&-chaining\n + docs/api-config: minor clarifications\n + docs: add a basic description of the config API\n\nAn assignment to the include.path pseudo-variable causes the named file\nto be included in-place when Git looks up configuration variables.\n\nReverted the earlier round from 'next' and then fixed up further.\n\n* ld/git-p4-expanded-keywords (2012-02-14) 1 commit\n  (merged to 'next' on 2012-02-16 at a9004c5)\n + git-p4: add initial support for RCS keywords\n\nTeach git-p4 to unexpand $RCS$-like keywords that are embedded in\ntracked contents in order to reduce unnecessary merge conflicts.\n\nIs this ready for 'master'?\n"}]}