{"thread":{"id":"42253","subject":"What's cooking in git.git (May 2016, #02; Fri, 6)","startedAt":"2016-05-06T22:46:13Z","lastAt":"2016-05-13T11:52:11Z","messageCount":9,"participants":["Junio C Hamano","Johannes Schindelin","Lars Schneider"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"285789","messageId":"xmqqeg9e24ay.fsf@gitster.mtv.corp.google.com","threadId":"42253","inReplyTo":null,"subject":"What's cooking in git.git (May 2016, #02; Fri, 6)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2016-05-06T22:46:13Z","receivedAt":"2016-05-06T22:46:13Z","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\n'-' are only in 'pu' (proposed updates) while commits prefixed with\n'+' are in 'next'.  The ones marked with '.' do not appear in any of\nthe integration branches, but I am still holding onto them.\n\nThe 'master' branch now has the tenth batch of topics of this cycle.\nOn the 'maint' front, 2.8.2 is out and fixes that have been in\n'master' accumulates on it for 2.8.3.\n\nOnes with questionable status has a '?' character in their comments.\n\nYou can find the changes described here in the integration branches\nof the repositories listed at\n\n    http://git-blame.blogspot.com/p/git-public-repositories.html\n\n--------------------------------------------------\n[Graduated to \"master\"]\n\n* bc/object-id (2016-04-25) 6 commits\n  (merged to 'next' on 2016-04-29 at 02f13a4)\n + match-trees: convert several leaf functions to use struct object_id\n + tree-walk: convert tree_entry_extract() to use struct object_id\n + struct name_entry: use struct object_id instead of unsigned char sha1[20]\n + match-trees: convert shift_tree() and shift_tree_by() to use object_id\n + test-match-trees: convert to use struct object_id\n + sha1-name: introduce a get_oid() function\n\n Move from unsigned char[20] to struct object_id continues.\n\n\n* bw/rebase-merge-entire-branch (2016-04-24) 1 commit\n  (merged to 'next' on 2016-04-29 at 7a9487f)\n + git-rebase--merge: don't include absent parent as a base\n\n \"git rebase -m\" could be asked to rebase an entire branch starting\n from the root, but failed by assuming that there always is a parent\n commit to the first commit on the branch.\n\n\n* jc/drop-git-spec-in (2016-04-27) 2 commits\n  (merged to 'next' on 2016-04-27 at 2b85030)\n + Makefile: remove dependency on git.spec\n  (merged to 'next' on 2016-04-22 at 531583f)\n + Makefile: stop pretending to support rpmbuild\n\n As nobody maintains our in-tree git.spec.in and distros use their\n own spec file, we stopped pretending that we support \"make rpm\".\n\n\n* jk/diff-compact-heuristic (2016-05-02) 3 commits\n  (merged to 'next' on 2016-05-02 at 2a74763)\n + diff: undocument the compaction heuristic knobs for experimentation\n  (merged to 'next' on 2016-04-22 at 0c117ea)\n + xdiff: implement empty line chunk heuristic\n + xdiff: add recs_match helper function\n (this branch is tangled with jc/diff-compact-always-use-blank-heuristics.)\n\n Patch output from \"git diff\" and friends has been tweaked to be\n more readable by using a blank line as a strong hint that the\n contents before and after it belong to a logically separate unit.\n\n\n* js/http-custom-headers (2016-04-27) 1 commit\n  (merged to 'next' on 2016-04-27 at 0c97a50)\n + http: support sending custom HTTP headers\n\n HTTP transport clients learned to throw extra HTTP headers at the\n server, specified via http.extraHeader configuration variable.\n\n\n* ld/p4-test-py3 (2016-04-26) 3 commits\n  (merged to 'next' on 2016-04-27 at d5d5fca)\n + git-p4 tests: time_in_seconds should use $PYTHON_PATH\n + git-p4 tests: work with python3 as well as python2\n + git-p4 tests: cd to / before running python\n\n The test scripts for \"git p4\" (but not \"git p4\" implementation\n itself) has been updated so that they would work even on a system\n where the installed version of Python is python 3.\n\n\n* ls/p4-lfs-test-fix-2.7.0 (2016-04-29) 2 commits\n  (merged to 'next' on 2016-04-29 at da56b67)\n + t9824: fix wrong reference value\n  (merged to 'next' on 2016-04-27 at be87c63)\n + t9824: fix broken &&-chain in a subshell\n\n Fix a broken test.\n\n\n* sb/clone-shallow-passthru (2016-04-26) 1 commit\n  (merged to 'next' on 2016-04-27 at 3112b24)\n + clone: add `--shallow-submodules` flag\n\n \"git clone\" learned \"--shallow-submodules\" option.\n\n\n* sb/config-exit-status-list (2016-04-26) 1 commit\n  (merged to 'next' on 2016-04-27 at 44fe343)\n + config doc: improve exit code listing\n\n Doc update.\n\n--------------------------------------------------\n[New Topics]\n\n* sb/submodule-deinit-all (2016-05-05) 1 commit\n - submodule deinit: require '--all' instead of '.' for all submodules\n\n Correct faulty recommendation to use \"git submodule deinit .\" when\n de-initialising all submodules, which would result in a strange\n error message in a pathological corner case.\n\n Will merge to 'next'.\n\n\n* bn/config-doc-tt-varnames (2016-05-05) 1 commit\n - config: consistently format $variables in monospaced font\n (this branch uses jc/config-pathname-type.)\n\n Doc formatting fixes.\n\n\n* lp/typofixes (2016-05-06) 1 commit\n - typofix: assorted typofixes in comments, documentation and messages\n\n Will merge to 'next'.\n\n\n* sb/z-is-gnutar-ism (2016-05-06) 1 commit\n - t3513: do not compress backup tar file\n\n Will merge to 'next'.\n\n\n* jc/test-parse-options-expect (2016-05-06) 4 commits\n - t0040: convert a few tests to use test-parse-options --expect\n - t0040: remove unused test helpers\n - test-parse-options: --expect=<string> option to simplify tests\n - test-parse-options: fix output when callback option fails\n (this branch uses pb/commit-verbose-config.)\n\n\n* jc/doc-lint (2016-05-04) 2 commits\n - Documentation: fix linkgit references\n - ci: validate \"gitlink:\" in documentation\n\n\n--------------------------------------------------\n[Stalled]\n\n* sb/bisect (2016-04-15) 22 commits\n - SQUASH???\n - bisect: get back halfway shortcut\n - bisect: compute best bisection in compute_relevant_weights()\n - bisect: use a bottom-up traversal to find relevant weights\n - bisect: prepare for different algorithms based on find_all\n - bisect: rename count_distance() to compute_weight()\n - bisect: make total number of commits global\n - bisect: introduce distance_direction()\n - bisect: extract get_distance() function from code duplication\n - bisect: use commit instead of commit list as arguments when appropriate\n - bisect: replace clear_distance() by unique markers\n - bisect: use struct node_data array instead of int array\n - bisect: get rid of recursion in count_distance()\n - bisect: make algorithm behavior independent of DEBUG_BISECT\n - bisect: make bisect compile if DEBUG_BISECT is set\n - bisect: plug the biggest memory leak\n - bisect: add test for the bisect algorithm\n - t6030: generalize test to not rely on current implementation\n - t: use test_cmp_rev() where appropriate\n - t/test-lib-functions.sh: generalize test_cmp_rev\n - bisect: allow 'bisect run' if no good commit is known\n - bisect: write about `bisect next` in documentation\n\n The internal algorithm used in \"git bisect\" to find the next commit\n to check has been optimized greatly.\n\n Expecting a reroll.\n ($gmane/291163)\n\n\n* ar/diff-args-osx-precompose (2016-04-05) 1 commit\n - diff: run arguments through precompose_argv\n\n Many commands normalize command line arguments from NFD to NFC\n variant of UTF-8 on OSX, but commands in the \"diff\" family did\n not, causing \"git diff $path\" to complain that no such path is\n known to Git.  They have been taught to do the normalization.\n\n Will this be rerolled?\n ($gmane/290724)\n\n\n* nd/shallow-deepen (2016-04-13) 26 commits\n - fetch, upload-pack: --deepen=N extends shallow boundary by N commits\n - upload-pack: add get_reachable_list()\n - upload-pack: split check_unreachable() in two, prep for get_reachable_list()\n - t5500, t5539: tests for shallow depth excluding a ref\n - clone: define shallow clone boundary with --shallow-exclude\n - fetch: define shallow boundary with --shallow-exclude\n - upload-pack: support define shallow boundary by excluding revisions\n - refs: add expand_ref()\n - t5500, t5539: tests for shallow depth since a specific date\n - clone: define shallow clone boundary based on time with --shallow-since\n - fetch: define shallow boundary with --shallow-since\n - upload-pack: add deepen-since to cut shallow repos based on time\n - shallow.c: implement a generic shallow boundary finder based on rev-list\n - fetch-pack: use a separate flag for fetch in deepening mode\n - fetch-pack.c: mark strings for translating\n - fetch-pack: use a common function for verbose printing\n - fetch-pack: use skip_prefix() instead of starts_with()\n - upload-pack: move rev-list code out of check_non_tip()\n - upload-pack: tighten number parsing at \"deepen\" lines\n - upload-pack: use skip_prefix() instead of starts_with()\n - upload-pack: move \"unshallow\" sending code out of deepen()\n - upload-pack: remove unused variable \"backup\"\n - upload-pack: move \"shallow\" sending code out of deepen()\n - upload-pack: move shallow deepen code out of receive_needs()\n - transport-helper.c: refactor set_helper_option()\n - remote-curl.c: convert fetch_git() to use argv_array\n\n The existing \"git fetch --depth=<n>\" option was hard to use\n correctly when making the history of an existing shallow clone\n deeper.  A new option, \"--deepen=<n>\", has been added to make this\n easier to use.  \"git clone\" also learned \"--shallow-since=<date>\"\n and \"--shallow-exclude=<tag>\" options to make it easier to specify\n \"I am interested only in the recent N months worth of history\" and\n \"Give me only the history since that version\".\n\n Needs review.\n\n\n* sg/completion-updates (2016-02-28) 21 commits\n - completion: cache the path to the repository\n - completion: extract repository discovery from __gitdir()\n - completion: don't guard git executions with __gitdir()\n - completion: consolidate silencing errors from git commands\n - completion: don't use __gitdir() for git commands\n - completion: respect 'git -C <path>'\n - completion: fix completion after 'git -C <path>'\n - completion: don't offer commands when 'git --opt' needs an argument\n - rev-parse: add '--absolute-git-dir' option\n - completion: list short refs from a remote given as a URL\n - completion: don't list 'HEAD' when trying refs completion outside of a repo\n - completion: list refs from remote when remote's name matches a directory\n - completion: respect 'git --git-dir=<path>' when listing remote refs\n - completion: fix most spots not respecting 'git --git-dir=<path>'\n - completion: ensure that the repository path given on the command line exists\n - completion tests: add tests for the __git_refs() helper function\n - completion tests: check __gitdir()'s output in the error cases\n - completion tests: consolidate getting path of current working directory\n - completion tests: make the $cur variable local to the test helper functions\n - completion tests: don't add test cruft to the test repository\n - completion: improve __git_refs()'s in-code documentation\n\n Will be rerolled.\n ($gmane/287839)\n\n\n* az/p4-bare-no-rebase (2016-02-19) 1 commit\n - git-p4.py: Don't try to rebase on submit from bare repository\n\n \"git p4 submit\" attempts to do a rebase, which would fail if done\n in a bare repository.  Not doing this rebase would paper over the\n failure, which is what this patch does, but it is unclear what the\n side effect of not rebasing is.\n\n Needs a better explanation.\n\n\n* ss/commit-dry-run-resolve-merge-to-no-op (2016-02-17) 1 commit\n - wt-status.c: set commitable bit if there is a meaningful merge.\n\n \"git commit --dry-run\" reported \"No, no, you cannot commit.\" in one\n case where \"git commit\" would have allowed you to commit, and this\n improves it a little bit (\"git commit --dry-run --short\" still does\n not give you the correct answer, for example).\n\n\n* nd/icase (2016-02-15) 12 commits\n - grep.c: reuse \"icase\" variable\n - diffcore-pickaxe: support case insensitive match on non-ascii\n - diffcore-pickaxe: \"share\" regex error handling code\n - grep/pcre: support utf-8\n - gettext: add is_utf8_locale()\n - grep/pcre: prepare locale-dependent tables for icase matching\n - grep/icase: avoid kwsset when -F is specified\n - grep/icase: avoid kwsset on literal non-ascii strings\n - test-regex: expose full regcomp() to the command line\n - test-regex: isolate the bug test code\n - grep: break down an \"if\" stmt in preparation for next changes\n - grep: allow -F -i combination\n\n \"git grep -i\" has been taught to fold case in non-ascii locales.\n\n Needs review.\n ($gmane/286137)\n\n\n* ec/annotate-deleted (2015-11-20) 1 commit\n - annotate: skip checking working tree if a revision is provided\n\n Usability fix for annotate-specific \"<file> <rev>\" syntax with deleted\n files.\n\n Waiting for review.\n\n\n* dg/subtree-rebase-test (2016-01-19) 1 commit\n - contrib/subtree: Add a test for subtree rebase that loses commits\n\n Reviewed up to v5.\n Will be rerolled.\n ($gmane/284426)\n\n\n* js/am-3-merge-recursive-direct (2015-10-12) 2 commits\n - am: make a direct call to merge_recursive\n - merge_recursive_options: introduce the \"gently\" flag\n\n The merge_recursive_generic() function has been made a bit safer to\n call from inside a process.  \"git am -3\" was taught to make a direct\n call to the function when falling back to three-way merge.\n\n Being able to make a direct call would be good in general, but as a\n performance thing, the change needs to be backed up by numbers.\n\n I haven't gone through the \"gently\" change with fine toothed comb;\n I can see that the change avoids calling die(), but I haven't made\n sure that the program states (e.g. what's in the in-core index) are\n adjusted sensibly when it returns to the caller instead of dying,\n or the codepaths that used to die() are free of resource leaks.\n The original code certainly did not care the program states at the\n point of dying exactly because it knew it is going to exit, but now\n they have to care, and they need to be audited.\n\n Will be rerolled.\n ($gmane/292205)\n\n\n* dk/gc-more-wo-pack (2016-01-13) 4 commits\n - gc: clean garbage .bitmap files from pack dir\n - t5304: ensure non-garbage files are not deleted\n - t5304: test .bitmap garbage files\n - prepare_packed_git(): find more garbage\n\n Follow-on to dk/gc-idx-wo-pack topic, to clean up stale\n .bitmap and .keep files.\n\n Waiting for a reroll.\n ($gmane/284368).\n\n\n* jc/diff-b-m (2015-02-23) 5 commits\n . WIPWIP\n . WIP: diff-b-m\n - diffcore-rename: allow easier debugging\n - diffcore-rename.c: add locate_rename_src()\n - diffcore-break: allow debugging\n\n \"git diff -B -M\" produced incorrect patch when the postimage of a\n completely rewritten file is similar to the preimage of a removed\n file; such a resulting file must not be expressed as a rename from\n other place.\n\n The fix in this patch is broken, unfortunately.\n Will discard.\n\n--------------------------------------------------\n[Cooking]\n\n* ew/normal-to-e (2016-05-02) 1 commit\n  (merged to 'next' on 2016-05-06 at 65a2c52)\n + .mailmap: update to my shorter email address\n\n Will merge to 'master'.\n\n\n* js/close-packs-before-gc (2016-05-02) 1 commit\n  (merged to 'next' on 2016-05-06 at bfd39bf)\n + t5510: run auto-gc in the foreground\n\n Will merge to 'master'.\n\n\n* ls/travis-submitting-patches (2016-05-02) 1 commit\n  (merged to 'next' on 2016-05-06 at 467930e)\n + Documentation: add setup instructions for Travis CI\n\n Will merge to 'master'.\n\n\n* rn/glossary-typofix (2016-05-02) 1 commit\n  (merged to 'next' on 2016-05-06 at 1e73e76)\n + Documentation: fix typo 'In such these cases'\n\n Will merge to 'master'.\n\n\n* jc/commit-tree-ignore-commit-gpgsign (2016-05-03) 1 commit\n  (merged to 'next' on 2016-05-06 at 08eccb2)\n + commit-tree: do not pay attention to commit.gpgsign\n\n \"git commit-tree\" plumbing command required the user to always sign\n its result when the user sets the commit.gpgsign configuration\n variable, which was an ancient mistake.  Rework \"git rebase\" that\n relied on this mistake so that it reads commit.gpgsign and pass (or\n not pass) the -S option to \"git commit-tree\" to keep the end-user\n expectation the same, while teaching \"git commit-tree\" to ignore\n the configuration variable.  This will stop requiring the users to\n sign commit objects used internally as an implementation detail of\n \"git stash\".\n\n Will merge to 'master'.\n\n\n* jk/push-client-deadlock-fix (2016-05-02) 1 commit\n  (merged to 'next' on 2016-05-06 at e91626c)\n + Windows: add pthread_sigmask() that does nothing\n\n Will merge to 'master'.\n\n\n* sb/clean-test-fix (2016-05-03) 1 commit\n  (merged to 'next' on 2016-05-06 at d80c9c6)\n + t7300: mark test with SANITY\n\n Will merge to 'master'.\n\n\n* sb/submodule-module-list-pathspec-fix (2016-05-03) 1 commit\n  (merged to 'next' on 2016-05-06 at ab6dac3)\n + submodule deinit test: fix broken && chain in subshell\n\n Will merge to 'master'.\n\n\n* sk/gitweb-highlight-encoding (2016-05-03) 1 commit\n  (merged to 'next' on 2016-05-06 at 441302c)\n + gitweb: apply fallback encoding before highlight\n\n Some multi-byte encoding can have a backslash byte as a later part\n of one letter, which would confuse \"highlight\" filter used in\n gitweb.\n\n Will merge to 'master'.\n\n\n* ab/hooks (2016-05-04) 4 commits\n - hooks: allow customizing where the hook directory is\n - githooks.txt: minor improvements to the grammar & phrasing\n - githooks.txt: amend dangerous advice about 'update' hook ACL\n - githooks.txt: improve the intro section\n\n A new configuration variable core.hooksPath allows customizing\n where the hook directory is.\n\n Will merge to 'next'.\n\n\n* jc/merge-impossible-no-commit (2016-04-26) 2 commits\n - merge: warn --no-commit merge when no new commit is created\n - merge: do not contaminate option_commit with --squash\n\n \"git merge --no-commit\" silently succeeded when there is no need to\n create any commit, either when you are more recent than the commit\n you tried to merge, or you can fast-forward to the commit you tried\n to merge.  The command gives a warning message in such cases.\n\n Just tying loose ends in a discussion.  Unless somebody else\n champions this topic, I'll drop it.\n\n\n* mh/split-under-lock (2016-05-06) 33 commits\n - lock_ref_sha1_basic(): only handle REF_NODEREF mode\n - commit_ref_update(): remove the flags parameter\n - lock_ref_for_update(): don't resolve symrefs\n - lock_ref_for_update(): don't re-read non-symbolic references\n - refs: resolve symbolic refs first\n - ref_transaction_update(): check refname_is_safe() at a minimum\n - unlock_ref(): move definition higher in the file\n - lock_ref_for_update(): new function\n - add_update(): initialize the whole ref_update\n - verify_refname_available(): adjust constness in declaration\n - refs: don't dereference on rename\n - refs: allow log-only updates\n - delete_branches(): use resolve_refdup()\n - ref_transaction_commit(): correctly report close_ref() failure\n - ref_transaction_create(): disallow recursive pruning\n - refs: make error messages more consistent\n - lock_ref_sha1_basic(): remove unneeded local variable\n - read_raw_ref(): move docstring to header file\n - read_raw_ref(): improve docstring\n - read_raw_ref(): rename symref argument to referent\n - read_raw_ref(): clear *type at start of function\n - read_raw_ref(): rename flags argument to type\n - ref_transaction_commit(): remove local variable n\n - rename_ref(): remove unneeded local variable\n - commit_ref_update(): write error message to *err, not stderr\n - refname_is_safe(): insist that the refname already be normalized\n - refname_is_safe(): don't allow the empty string\n - refname_is_safe(): use skip_prefix()\n - remove_dir_recursively(): add docstring\n - safe_create_leading_directories(): improve docstring\n - read_raw_ref(): don't get confused by an empty directory\n - commit_ref(): if there is an empty dir in the way, delete it\n - t1404: demonstrate a bug resolving references\n\n Further preparatory work on the refs API before the pluggable\n backend series can land.\n\n Updated.  Will wait for comments for the last time, and then\n merge to 'next'.\n\n\n* bn/http-cookiefile-config (2016-05-04) 2 commits\n - http: expand http.cookieFile as a path\n - Documentation: config: improve word ordering for http.cookieFile\n\n \"http.cookieFile\" configuration variable clearly wants a pathname,\n but we forgot to treat it as such by e.g. applying tilde expansion.\n\n Will merge to 'next'.\n\n\n* ew/doc-split-pack-disables-bitmap (2016-04-28) 1 commit\n  (merged to 'next' on 2016-05-06 at 6343d1e)\n + pack-objects: warn on split packs disabling bitmaps\n\n Doc update.\n\n Will merge to 'master'.\n\n\n* jc/config-pathname-type (2016-05-04) 1 commit\n - config: describe 'pathname' value type\n (this branch is used by bn/config-doc-tt-varnames.)\n\n Consolidate description of tilde-expansion that is done to\n configuration variables that take pathname to a single place.\n\n Will merge to 'next'.\n\n\n* jk/submodule-c-credential (2016-05-06) 6 commits\n - submodule: stop sanitizing config options\n - submodule: use prepare_submodule_repo_env consistently\n - submodule--helper: move config-sanitizing to submodule.c\n - submodule: export sanitized GIT_CONFIG_PARAMETERS\n - t5550: break submodule config test into multiple sub-tests\n - t5550: fix typo in $HTTPD_URL\n\n An earlier addition of \"sanitize_submodule_env\" with 14111fc4 (git:\n submodule honor -c credential.* from command line, 2016-02-29)\n turned out to be a convoluted no-op; implement what it wanted to do\n correctly.\n\n Everybody happy?\n\n\n* mh/connect-leak (2016-04-28) 1 commit\n - git_connect(): fix memory leak with CONNECT_DIAG_URL\n\n Is already made obsolete with a patch in flight under discussion.\n ($gmane/292962)\n\n Will discard.\n\n\n* sb/misc-cleanups (2016-04-28) 2 commits\n  (merged to 'next' on 2016-05-06 at 87bc8a5)\n + submodule-config: don't shadow `cache`\n + config.c: drop local variable\n\n Will merge to 'master'.\n\n\n* ew/fast-import-unpack-limit (2016-04-24) 1 commit\n - fast-import: implement unpack limit\n\n \"git fast-import\" learned the same performance trick to avoid\n creating too small a packfile as \"git fetch\" and \"git push\" have,\n using *.unpackLimit configuration.\n\n Need to pick up the rerolled version.\n ($gmane/292562)\n\n\n* ls/p4-lfs (2016-04-28) 3 commits\n  (merged to 'next' on 2016-05-06 at 3e1354d)\n + git-p4: fix Git LFS pointer parsing\n + travis-ci: express Linux/OS X dependency versions more clearly\n + travis-ci: update Git-LFS and P4 to the latest version\n\n Recent update to Git LFS broke \"git p4\" by changing the output from\n its \"lfs pointer\" subcommand.\n\n Will merge to 'master'.\n\n\n* tb/convert-eol-autocrlf (2016-04-29) 10 commits\n - ce_compare_data() did not respect conversion\n - t6038; use crlf on all platforms\n - convert.c: more safer crlf handling with text attribute\n - convert: unify the \"auto\" handling of CRLF\n - convert.c: stream and early out\n - read-cache: factor out get_sha1_from_index() helper\n - convert.c: ident + core.autocrlf didn't work\n - t0027: test cases for combined attributes\n - convert: allow core.autocrlf=input and core.eol=crlf\n - t0027: make commit_chk_wrnNNO() reliable\n\n The combination of text=auto & eol=crlf (or eol=lf for that matter)\n is taught to be much more useful; it used to be \"auto detection\"\n was defeated as if setting eol declares that the file _is_ text,\n but now text=auto is still in effect for such a path and the code\n refrains from applying eol conversion if it found the path is not\n text.  Also setting core.autocrlf to 'input' and core.eol to 'crlf'\n used to be rejected, but because the code gives precedence to\n core.autocrlf, there is no need to, hence we no longer reject the\n combination.\n\n Earlier steps looked alright, but it veers into a wrong direction\n in the middle.\n\n\n* ep/http-curl-trace (2016-05-02) 2 commits\n . imap-send.c: introduce the GIT_TRACE_CURL environment variable\n . http.c: implement the GIT_TRACE_CURL environment variable\n\n HTTP transport gained an option to produce more detailed debugging\n trace.\n\n Still under discussion.\n ($gmane/292074, 293236)\n\n\n* nd/worktree-various-heads (2016-04-22) 13 commits\n - branch: do not rename a branch under bisect or rebase\n - worktree.c: check whether branch is bisected in another worktree\n - wt-status.c: split bisect detection out of wt_status_get_state()\n - worktree.c: check whether branch is rebased in another worktree\n - worktree.c: avoid referencing to worktrees[i] multiple times\n - wt-status.c: make wt_status_check_rebase() work on any worktree\n - wt-status.c: split rebase detection out of wt_status_get_state()\n - path.c: refactor and add worktree_git_path()\n - worktree.c: mark current worktree\n - worktree.c: make find_shared_symref() return struct worktree *\n - worktree.c: store \"id\" instead of \"git_dir\"\n - path.c: add git_common_path() and strbuf_git_common_path()\n - dir.c: rename str(n)cmp_icase to fspath(n)cmp\n\n The experimental \"multiple worktree\" feature gains more safety to\n forbid operations on a branch that is checked out or being actively\n worked on elsewhere, by noticing that e.g. it is being rebased.\n\n Being reviewed.\n ($gmane/292189)\n\n\n* pb/commit-verbose-config (2016-05-05) 8 commits\n - SQUASH???\n - commit: add a commit.verbose config variable\n - t7507-commit-verbose: improve test coverage by testing number of diffs\n - parse-options.c: make OPTION_COUNTUP respect \"unspecified\" values\n - t/t7507: improve test coverage\n - t0040-parse-options: improve test coverage\n - test-parse-options: print quiet as integer\n - t0040-test-parse-options.sh: fix style issues\n (this branch is used by jc/test-parse-options-expect.)\n\n \"git commit\" learned to pay attention to \"commit.verbose\"\n configuration variable and act as if \"--verbose\" option was\n given from the command line.\n\n Almost there.\n ($gmane/293663).\n\n\n* jc/fsck-nul-in-commit (2016-04-14) 2 commits\n - fsck: detect and warn a commit with embedded NUL\n - fsck_commit_buffer(): do not special case the last validation\n\n \"git fsck\" learned to catch NUL byte in a commit object as\n potential error and warn.\n\n What was the status of this one?  Ready to proceed?\n\n\n* jc/ll-merge-internal (2016-04-27) 3 commits\n - t6036: remove pointless test that expects failure\n - ll-merge: use a longer conflict marker for internal merge\n - ll-merge: fix typo in comment\n\n \"git rerere\" can get confused by conflict markers deliberately left\n by the inner merge step, because they are indistinguishable from\n the real conflict markers left by the outermost merge which are\n what the end user and \"rerere\" need to look at.  This was fixed by\n making the conflict markers left by the inner merges a bit longer.\n\n Will rebase to remove the comment after three-dash line and then merge.\n\n\n* sb/submodule-init (2016-05-03) 7 commits\n  (merged to 'next' on 2016-05-03 at 8a5fce4)\n + submodule init: redirect stdout to stderr\n  (merged to 'next' on 2016-04-29 at 3e81ee88)\n + submodule--helper update-clone: abort gracefully on missing .gitmodules\n + submodule init: fail gracefully with a missing .gitmodules file\n  (merged to 'next' on 2016-04-27 at afaad81)\n + submodule: port init from shell to C\n + submodule: port resolve_relative_url from shell to C\n + Merge branch 'sb/submodule-path-misc-bugs' into sb/submodule-init\n + Merge branch 'sb/submodule-helper-clone-regression-fix' into sb/submodule-init\n\n Update of \"git submodule\" to move pieces of logic to C continues.\n\n Will cook for a bit more in 'next'.\n\n\n* jc/send-email-skip-backup (2016-04-12) 1 commit\n - send-email: detect and offer to skip backup files\n\n A careless invocation of \"git send-email directory/\" after editing\n 0001-change.patch with an editor often ends up sending both\n 0001-change.patch and its backup file, 0001-change.patch~, causing\n embarrassment and a minor confusion.  Detect such an input and\n offer to skip the backup files when sending the patches out.\n\n Needs review.\n\n\n* va/i18n-misc-updates (2016-04-19) 9 commits\n - i18n: builtin/pull.c: split strings marked for translation\n - i18n: builtin/pull.c: mark placeholders for translation\n - i18n: git-parse-remote.sh: mark strings for translation\n - i18n: branch: move comment for translators\n - i18n: branch: unmark string for translation\n - i18n: builtin/rm.c: remove a comma ',' from string\n - i18n: unpack-trees: mark strings for translation\n - i18n: builtin/branch.c: mark option for translation\n - i18n: index-pack: use plural string instead of normal one\n\n Mark several messages for translation.\n\n Comments?  They looked all sensible to me.\n Does the lack of response mean lack of interest and support?\n\n\n* kn/ref-filter-branch-list (2016-04-25) 17 commits\n - branch: implement '--format' option\n - branch: use ref-filter printing APIs\n - branch, tag: use porcelain output\n - ref-filter: allow porcelain to translate messages in the output\n - ref-filter: add `:dir` and `:base` options for ref printing atoms\n - ref-filter: make remote_ref_atom_parser() use refname_atom_parser_internal()\n - ref-filter: introduce symref_atom_parser() and refname_atom_parser()\n - ref-filter: introduce refname_atom_parser_internal()\n - ref-filter: make \"%(symref)\" atom work with the ':short' modifier\n - ref-filter: add support for %(upstream:track,nobracket)\n - ref-filter: make %(upstream:track) prints \"[gone]\" for invalid upstreams\n - ref-filter: introduce format_ref_array_item()\n - ref-filter: move get_head_description() from branch.c\n - ref-filter: modify \"%(objectname:short)\" to take length\n - ref-filter: implement %(if:equals=<string>) and %(if:notequals=<string>)\n - ref-filter: include reference to 'used_atom' within 'atom_value'\n - ref-filter: implement %(if), %(then), and %(else) atoms\n\n The code to list branches in \"git branch\" has been consolidated\n with the more generic ref-filter API.\n\n Needs review.\n\n\n* xy/format-patch-base (2016-04-26) 4 commits\n - format-patch: introduce format.useAutoBase configuration\n - format-patch: introduce --base=auto option\n - format-patch: add '--base' option to record base tree info\n - patch-ids: make commit_patch_id() a public helper function\n\n \"git format-patch\" learned a new \"--base\" option to record what\n (public, well-known) commit the original series was built on in\n its output.\n\n Looking close to be ready.\n ($gmane/292622).\n\n\n* dt/index-helper (2016-05-05) 19 commits\n - untracked-cache: config option\n - trace: measure where most of the time is spent\n - index-helper: optionally automatically run\n - index-helper: autorun mode\n - index-helper: don't run if already running\n - index-helper: kill mode\n - watchman: add a config option to enable the extension\n - unpack-trees: preserve index extensions\n - update-index: enable/disable watchman support\n - index-helper: use watchman to avoid refreshing index with lstat()\n - watchman: add support to watchman to reduce refresh cost\n - read-cache: add watchman 'WAMA' extension\n - index-helper: add --detach\n - daemonize(): set a flag before exiting the main process\n - index-helper: log warnings\n - index-helper: add --strict\n - index-helper: new daemon for caching index and related stuff\n - read-cache: allow to keep mmap'd memory after reading\n - read-cache.c: fix constness of verify_hdr()\n\n Needs review.  Reported to break its own tests.\n ($gmane/293687).\n\n\n* jc/bundle (2016-03-03) 6 commits\n - index-pack: --clone-bundle option\n - Merge branch 'jc/index-pack' into jc/bundle\n - bundle v3: the beginning\n - bundle: keep a copy of bundle file name in the in-core bundle header\n - bundle: plug resource leak\n - bundle doc: 'verify' is not about verifying the bundle\n\n The beginning of \"split bundle\", which could be one of the\n ingredients to allow \"git clone\" traffic off of the core server\n network to CDN.\n\n\n* jc/merge-drop-old-syntax (2015-04-29) 1 commit\n - merge: drop 'git merge <message> HEAD <commit>' syntax\n\n Stop supporting \"git merge <message> HEAD <commit>\" syntax that has\n been deprecated since October 2007, and issues a deprecation\n warning message since v2.5.0.\n\n It has been reported that git-gui still uses the deprecated syntax,\n which needs to be fixed before this final step can proceed.\n ($gmane/282594)\n\n--------------------------------------------------\n[Discarded]\n\n* jc/diff-compact-always-use-blank-heuristics (2016-04-29) 1 commit\n . diff: enable \"compaction heuristics\" and lose experimentation knob\n\n Superseded by the tip commit on the jk/diff-compact-heuristic topic.\n"},{"id":"286017","messageId":"alpine.DEB.2.20.1605100751050.4092@virtualbox","threadId":"42253","inReplyTo":"xmqqeg9e24ay.fsf@gitster.mtv.corp.google.com","subject":"Re: What's cooking in git.git (May 2016, #02; Fri, 6)","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2016-05-10T05:52:18Z","receivedAt":"2016-05-10T05:52:18Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Junio,\n\nOn Fri, 6 May 2016, Junio C Hamano wrote:\n\n> * jk/submodule-c-credential (2016-05-06) 6 commits\n>  - submodule: stop sanitizing config options\n>  - submodule: use prepare_submodule_repo_env consistently\n>  - submodule--helper: move config-sanitizing to submodule.c\n>  - submodule: export sanitized GIT_CONFIG_PARAMETERS\n>  - t5550: break submodule config test into multiple sub-tests\n>  - t5550: fix typo in $HTTPD_URL\n> \n>  An earlier addition of \"sanitize_submodule_env\" with 14111fc4 (git:\n>  submodule honor -c credential.* from command line, 2016-02-29)\n>  turned out to be a convoluted no-op; implement what it wanted to do\n>  correctly.\n> \n>  Everybody happy?\n\nI cannot speak for everybody. I am happy, though. In particular with this\ntopic branch ;-)\n\nCiao,\nDscho\n"},{"id":"286018","messageId":"alpine.DEB.2.20.1605100757410.4092@virtualbox","threadId":"42253","inReplyTo":"xmqqeg9e24ay.fsf@gitster.mtv.corp.google.com","subject":"Re: What's cooking in git.git (May 2016, #02; Fri, 6)","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2016-05-10T05:59:35Z","receivedAt":"2016-05-10T05:59:35Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Junio,\n\nOn Fri, 6 May 2016, Junio C Hamano wrote:\n\n> * jc/fsck-nul-in-commit (2016-04-14) 2 commits\n>  - fsck: detect and warn a commit with embedded NUL\n>  - fsck_commit_buffer(): do not special case the last validation\n> \n>  \"git fsck\" learned to catch NUL byte in a commit object as\n>  potential error and warn.\n> \n>  What was the status of this one?  Ready to proceed?\n\nI think this code looks fine. Maybe two comments on the test:\n\n>               test_must_fail git -c fsck.nulInCommit=error fsck 2>warn.1 &&\n>               git fsck 2>warn.2 &&\n>               grep nulInCommit warn.2\n\n1) warn.1 is not used. Maybe skip that redirection?\n\n2) I was under the impression that we preferred test_i18ngrep over grep...\n\nThanks,\nDscho\n"},{"id":"286021","messageId":"B50A244E-05FE-48FF-9C9B-ED7AE35C5C7C@gmail.com","threadId":"42253","inReplyTo":"xmqqeg9e24ay.fsf@gitster.mtv.corp.google.com","subject":"Re: What's cooking in git.git (May 2016, #02; Fri, 6)","fromName":"Lars Schneider","fromEmail":"larsxschneider@gmail.com","sentAt":"2016-05-10T06:27:28Z","receivedAt":"2016-05-10T06:27:28Z","isPatch":false,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"\n> On 07 May 2016, at 00:46, Junio C Hamano <gitster@pobox.com> wrote:\n> \n> [...]\n> \n> \n> * jc/doc-lint (2016-05-04) 2 commits\n> - Documentation: fix linkgit references\n> - ci: validate \"gitlink:\" in documentation\n\nThe first patch \"Documentation: fix linkgit references\" seems not\nto be on the jc/doc-lint branch?\n\nA version with at least one section error is here:\nhttp://article.gmane.org/gmane.comp.version-control.git/293521\nShould I fix and reroll this patch?\n\nThe Travis-CI documentation check build step did not make it in:\nhttp://article.gmane.org/gmane.comp.version-control.git/293523\nIs there something I can improve?\n\nThis is how it looks like:\nhttps://travis-ci.org/larsxschneider/git/jobs/127733001\n\nThanks,\nLars\n"},{"id":"286032","messageId":"xmqq37pqs7qq.fsf@gitster.mtv.corp.google.com","threadId":"42253","inReplyTo":"B50A244E-05FE-48FF-9C9B-ED7AE35C5C7C@gmail.com","subject":"Re: What's cooking in git.git (May 2016, #02; Fri, 6)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2016-05-10T07:16:29Z","receivedAt":"2016-05-10T07:16:29Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Lars Schneider <larsxschneider@gmail.com> writes:\n\n>> On 07 May 2016, at 00:46, Junio C Hamano <gitster@pobox.com> wrote:\n>> \n>> [...]\n>> \n>> \n>> * jc/doc-lint (2016-05-04) 2 commits\n>> - Documentation: fix linkgit references\n>> - ci: validate \"gitlink:\" in documentation\n>\n> The first patch \"Documentation: fix linkgit references\" seems not\n> to be on the jc/doc-lint branch?\n\n* jc/linkgit-fix (2016-05-09) 1 commit\n - Documentation: fix linkgit references\n\n Many 'linkgit:<git documentation page>' references were broken,\n which are all fixed with this.\n\nI didn't want to keep the documentation fix hostage of the linter\nimprovements.  The linter implementation I am not entirely happy\nwith, but it did its job well enough that the broken references have\nbeen (hopefully all) identified, and I queued the fix separately.\n"},{"id":"286034","messageId":"xmqqy47iqszk.fsf@gitster.mtv.corp.google.com","threadId":"42253","inReplyTo":"alpine.DEB.2.20.1605100757410.4092@virtualbox","subject":"Re: What's cooking in git.git (May 2016, #02; Fri, 6)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2016-05-10T07:20:31Z","receivedAt":"2016-05-10T07:20:31Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:\n\n> On Fri, 6 May 2016, Junio C Hamano wrote:\n>\n>> * jc/fsck-nul-in-commit (2016-04-14) 2 commits\n>>  - fsck: detect and warn a commit with embedded NUL\n>>  - fsck_commit_buffer(): do not special case the last validation\n>> \n>>  \"git fsck\" learned to catch NUL byte in a commit object as\n>>  potential error and warn.\n>> \n>>  What was the status of this one?  Ready to proceed?\n>\n> I think this code looks fine. Maybe two comments on the test:\n>\n>>               test_must_fail git -c fsck.nulInCommit=error fsck 2>warn.1 &&\n>>               git fsck 2>warn.2 &&\n>>               grep nulInCommit warn.2\n>\n> 1) warn.1 is not used. Maybe skip that redirection?\n\nOr check it for expected result.  I don't know offhand which is better.\n\n> 2) I was under the impression that we preferred test_i18ngrep over grep...\n\nOnly when the strings we are expecting are subject to i18n.  I\nsomehow did not think your report() codepath has any i18n/l10n?\n"},{"id":"286076","messageId":"xmqqtwi5rgeb.fsf@gitster.mtv.corp.google.com","threadId":"42253","inReplyTo":"B50A244E-05FE-48FF-9C9B-ED7AE35C5C7C@gmail.com","subject":"Re: What's cooking in git.git (May 2016, #02; Fri, 6)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2016-05-10T17:07:08Z","receivedAt":"2016-05-10T17:07:08Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Lars Schneider <larsxschneider@gmail.com> writes:\n\n> A version with at least one section error is here:\n> http://article.gmane.org/gmane.comp.version-control.git/293521\n> Should I fix and reroll this patch?\n\nI just compared this with jc/linkgit-fix, which was done until the\nscript introduced by jc/doc-lint gets happy.  293521 covers the same\nspots, but misses the incorrect section numbers, so your reroll of it\nwould end up looking exactly like jc/linkgit-fix, I would think.\n\n> The Travis-CI documentation check build step did not make it in:\n> http://article.gmane.org/gmane.comp.version-control.git/293523\n> Is there something I can improve?\n\nLet me take another look later.\n\nThanks for carefully going through the \"What's cooking\" report.  It\nreally helps to make sure we move forward topics that need to.\n"},{"id":"286156","messageId":"D959E215-A37B-4F2E-AE09-FA4055E886CE@gmail.com","threadId":"42253","inReplyTo":"alpine.DEB.2.20.1605100751050.4092@virtualbox","subject":"Re: What's cooking in git.git (May 2016, #02; Fri, 6)","fromName":"Lars Schneider","fromEmail":"larsxschneider@gmail.com","sentAt":"2016-05-11T07:41:58Z","receivedAt":"2016-05-11T07:41:58Z","isPatch":false,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"\n> On 10 May 2016, at 07:52, Johannes Schindelin <johannes.schindelin@gmx.de> wrote:\n> \n> Hi Junio,\n> \n> On Fri, 6 May 2016, Junio C Hamano wrote:\n> \n>> * jk/submodule-c-credential (2016-05-06) 6 commits\n>> - submodule: stop sanitizing config options\n>> - submodule: use prepare_submodule_repo_env consistently\n>> - submodule--helper: move config-sanitizing to submodule.c\n>> - submodule: export sanitized GIT_CONFIG_PARAMETERS\n>> - t5550: break submodule config test into multiple sub-tests\n>> - t5550: fix typo in $HTTPD_URL\n>> \n>> An earlier addition of \"sanitize_submodule_env\" with 14111fc4 (git:\n>> submodule honor -c credential.* from command line, 2016-02-29)\n>> turned out to be a convoluted no-op; implement what it wanted to do\n>> correctly.\n>> \n>> Everybody happy?\n> \n> I cannot speak for everybody. I am happy, though. In particular with this\n> topic branch ;-)\n\nI want to second both statements :)\nThis topic branch solves a Git LFS submodule cloning issue nicely [1].\n\nThanks,\nLars\n\n[1] https://github.com/github/git-lfs/issues/1172#issuecomment-218384460\n"},{"id":"286447","messageId":"alpine.DEB.2.20.1605131349020.4092@virtualbox","threadId":"42253","inReplyTo":"xmqqy47iqszk.fsf@gitster.mtv.corp.google.com","subject":"Re: What's cooking in git.git (May 2016, #02; Fri, 6)","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2016-05-13T11:52:11Z","receivedAt":"2016-05-13T11:52:11Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Junio,\n\nOn Tue, 10 May 2016, Junio C Hamano wrote:\n\n> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:\n> \n> > On Fri, 6 May 2016, Junio C Hamano wrote:\n> >\n> > 2) I was under the impression that we preferred test_i18ngrep over grep...\n> \n> Only when the strings we are expecting are subject to i18n.  I\n> somehow did not think your report() codepath has any i18n/l10n?\n\nI finally remembered why I thought that test_i18ngrep was to be preferred\nover grep. For years, Git for Windows carried a patch that introduced a\nspecial `cmp` for use with text files, so that differences in the\nend-of-line markers could be ignored. IIRC we abandoned this when\ntest_i18ncmp learned to perform this trick. Only that it really is\ntest_cmp that learned this trick... so I was wrong.\n\nSo please forget what I said about this part of the patch.\n\nCiao,\nDscho\n"}]}