{"thread":{"id":"46299","subject":"What's cooking in git.git (Jun 2017, #09; Fri, 30)","startedAt":"2017-06-30T21:51:35Z","lastAt":"2017-07-05T16:22:30Z","messageCount":11,"participants":["Junio C Hamano","Ævar Arnfjörð Bjarmason","Torsten Bögershausen","Philip Oakley","Stefan Beller"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"323648","messageId":"xmqqk23tp2jk.fsf@gitster.mtv.corp.google.com","threadId":"46299","inReplyTo":null,"subject":"What's cooking in git.git (Jun 2017, #09; Fri, 30)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2017-06-30T21:51:27Z","receivedAt":"2017-06-30T21:51:35Z","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\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* ab/die-errors-in-threaded (2017-06-21) 1 commit\n  (merged to 'next' on 2017-06-24 at 135fc4b963)\n + die(): stop hiding errors due to overzealous recursion guard\n\n Traditionally, the default die() routine had a code to prevent it\n from getting called multiple times, which interacted badly when a\n threaded program used it (one downside is that the real error may\n be hidden and instead the only error message given to the user may\n end up being \"die recursion detected\", which is not very useful).\n\n\n* ah/doc-pretty-color-auto-prefix (2017-06-24) 1 commit\n  (merged to 'next' on 2017-06-26 at d7489fc831)\n + doc: clarify syntax for %C(auto,...) in pretty formats\n\n Doc update.\n\n\n* jc/pack-bitmap-unaligned (2017-06-26) 1 commit\n  (merged to 'next' on 2017-06-28 at ad026b12a3)\n + pack-bitmap: don't perform unaligned memory access\n\n An unaligned 32-bit access in pack-bitmap code ahs been corrected.\n\n\n* ks/status-initial-commit (2017-06-21) 1 commit\n  (merged to 'next' on 2017-06-24 at 940ffd5816)\n + status: contextually notify user about an initial commit\n\n \"git status\" has long shown essentially the same message as \"git\n commit\"; the message it gives while preparing for the root commit,\n i.e. \"Initial commit\", was hard to understand for some new users.\n Now it says \"No commits yet\" to stress more on the current status\n (rather than the commit the user is preparing for, which is more in\n line with the focus of \"git commit\").\n\n\n* ks/submodule-add-doc (2017-06-22) 1 commit\n  (merged to 'next' on 2017-06-24 at 26309b38f2)\n + Documentation/git-submodule: cleanup \"add\" section\n\n Doc update.\n\n\n* pw/rebase-i-regression-fix-tests (2017-06-23) 5 commits\n  (merged to 'next' on 2017-06-23 at 835ae762f5)\n + t3420: fix under GETTEXT_POISON build\n  (merged to 'next' on 2017-06-22 at d1dde1672a)\n + rebase: add more regression tests for console output\n + rebase: add regression tests for console output\n + rebase -i: add test for reflog message\n + sequencer: print autostash messages to stderr\n\n Fix a recent regression to \"git rebase -i\" and add tests that would\n have caught it and others.\n\n\n* rs/apply-validate-input (2017-06-27) 3 commits\n  (merged to 'next' on 2017-06-28 at 81e006b50e)\n + apply: check git diffs for mutually exclusive header lines\n + apply: check git diffs for invalid file modes\n + apply: check git diffs for missing old filenames\n\n Tighten error checks for invalid \"git apply\" input.\n\n\n* vs/typofixes (2017-06-27) 1 commit\n  (merged to 'next' on 2017-06-28 at 3d11e0b3fa)\n + Spelling fixes\n\n Many typofixes.\n\n--------------------------------------------------\n[New Topics]\n\n* ab/grep-lose-opt-regflags (2017-06-30) 6 commits\n - grep: remove redundant REG_NEWLINE when compiling fixed regex\n - grep: remove regflags from the public grep_opt API\n - grep: remove redundant and verbose re-assignments to 0\n - grep: remove redundant \"fixed\" field re-assignment to 0\n - grep: adjust a redundant grep pattern type assignment\n - grep: remove redundant double assignment to 0\n\n Code cleanup.\n\n Will merge to 'next'.\n\n\n* ks/commit-assuming-only-warning-removal (2017-06-30) 2 commits\n - commit-template: distinguish status information unconditionally\n - commit-template: remove outdated notice about explicit paths\n\n An old message shown in the commit log template was removed, as it\n has outlived its usefulness.\n\n Will merge to 'next'.\n\n\n* sb/hashmap-customize-comparison (2017-06-30) 3 commits\n - hashmap: migrate documentation from Documentation/technical into header\n - patch-ids.c: use hashmap correctly\n - hashmap.h: compare function has access to a data field\n (this branch is used by sb/diff-color-move.)\n\n Update the hashmap API so that data to customize the behaviour of\n the comparison function can be specified at the time a hashmap is\n initialized.  This fixes a bug in patch-ids that may have caused\n segfault.\n\n\n* sb/merge-recursive-code-cleanup (2017-06-30) 1 commit\n - merge-recursive: use DIFF_XDL_SET macro\n\n Code clean-up.\n\n Will merge to 'next'.\n\n--------------------------------------------------\n[Stalled]\n\n* mg/status-in-progress-info (2017-05-10) 2 commits\n - status --short --inprogress: spell it as --in-progress\n - status: show in-progress info for short status\n\n \"git status\" learns an option to report various operations\n (e.g. \"merging\") that the user is in the middle of.\n\n cf. <xmqqmvakcdqw.fsf@gitster.mtv.corp.google.com>\n\n\n* nd/worktree-move (2017-04-20) 6 commits\n - worktree remove: new command\n - worktree move: refuse to move worktrees with submodules\n - worktree move: accept destination as directory\n - worktree move: new command\n - worktree.c: add update_worktree_location()\n - worktree.c: add validate_worktree()\n\n \"git worktree\" learned move and remove subcommands.\n\n Expecting a reroll.\n cf. <20170420101024.7593-1-pclouds@gmail.com>\n cf. <20170421145916.mknekgqzhxffu7di@sigill.intra.peff.net>\n cf. <d0e81b1e-5869-299e-f462-4d43dc997bd1@ramsayjones.plus.com>\n\n\n* xz/send-email-batch-size (2017-05-23) 1 commit\n - send-email: --batch-size to work around some SMTP server limit\n\n \"git send-email\" learned to overcome some SMTP server limitation\n that does not allow many pieces of e-mails to be sent over a single\n session.\n\n Waiting for a response.\n cf. <CACBZZX5GYV50rjg9X602JHqFPaoofH9TwDf_-r_MDu8-rmNV6Q@mail.gmail.com>\n cf. <xmqqo9tfff2w.fsf@gitster.mtv.corp.google.com>\n\n \"\"\"I thought your wish (which I found reasonable) was to record\n whatever information that would help us in the future in the log\n message?  I was waiting for that to happen.\"\"\"\n\n\n* sg/clone-refspec-from-command-line-config (2017-06-16) 2 commits\n - Documentation/clone: document ignored configuration variables\n - clone: respect additional configured fetch refspecs during initial fetch\n (this branch is used by sg/remote-no-string-refspecs.)\n\n \"git clone -c var=val\" is a way to set configuration variables in\n the resulting repository, but it is more useful to also make these\n variables take effect while the initial clone is happening,\n e.g. these configuration variables could be fetch refspecs.\n\n Waiting for a response.\n cf. <20170617112228.vugswym4o4owf6wj@sigill.intra.peff.net>\n cf. <xmqqmv8zhdap.fsf@gitster.mtv.corp.google.com>\n\n\n* js/rebase-i-final (2017-06-15) 10 commits\n - rebase -i: rearrange fixup/squash lines using the rebase--helper\n - t3415: test fixup with wrapped oneline\n - rebase -i: skip unnecessary picks using the rebase--helper\n - rebase -i: check for missing commits in the rebase--helper\n - t3404: relax rebase.missingCommitsCheck tests\n - rebase -i: also expand/collapse the SHA-1s via the rebase--helper\n - rebase -i: do not invent onelines when expanding/collapsing SHA-1s\n - rebase -i: remove useless indentation\n - rebase -i: generate the script via rebase--helper\n - t3415: verify that an empty instructionFormat is handled as before\n\n The final batch to \"git rebase -i\" updates to move more code from\n the shell script to C.\n\n Expecting a reroll.\n This is at its v5.\n cf. <cover.1497444257.git.johannes.schindelin@gmx.de>\n\n--------------------------------------------------\n[Cooking]\n\n* ab/strbuf-addftime-tzname-boolify (2017-06-24) 3 commits\n - REWORD ONLY SQUASH\n - strbuf: change an always NULL/\"\" strbuf_addftime() param to bool\n - strbuf.h comment: discuss strbuf_addftime() arguments in order\n\n strbuf_addftime() is further getting tweaked.\n\n Waiting for a response.\n cf. <xmqqk2419rhg.fsf@gitster.mtv.corp.google.com>\n\n\n* mt/p4-parse-G-output (2017-06-27) 1 commit\n . git-p4: parse marshal output \"p4 -G\" in p4 changes\n\n Use \"p4 -G\" to make \"p4 changes\" output more Python-friendly\n to parse.\n\n Needs review/ack from git-p4 folks.\n\n\n* aw/contrib-subtree-doc-asciidoctor (2017-06-27) 1 commit\n  (merged to 'next' on 2017-06-30 at af23bd111b)\n + subtree: honour USE_ASCIIDOCTOR when set\n\n The Makefile rule in contrib/subtree for building documentation\n learned to honour USE_ASCIIDOCTOR just like the main documentation\n set does.\n\n Will merge to 'master'.\n\n\n* js/fsck-name-object (2017-06-28) 1 commit\n  (merged to 'next' on 2017-06-30 at 9a08514cf2)\n + t1450: use egrep for regexp \"alternation\"\n\n Test fix.\n\n Will merge to 'master'.\n\n\n* jc/utf8-fprintf (2017-06-28) 1 commit\n  (merged to 'next' on 2017-06-30 at a8cc490818)\n + submodule--helper: do not call utf8_fprintf() unnecessarily\n\n Code cleanup.\n\n Will merge to 'master'.\n\n\n* rs/free-and-null (2017-06-29) 1 commit\n - coccinelle: polish FREE_AND_NULL rules\n\n Code cleanup.\n\n\n* ab/wildmatch (2017-06-23) 1 commit\n - wildmatch: remove unused wildopts parameter\n\n Prepare the wildmatch API for future enhancements to allow a\n pattern that is repeatedly matched against many strings to be\n precompiled.\n\n\n* cc/shared-index-permfix (2017-06-25) 3 commits\n  (merged to 'next' on 2017-06-26 at bb41584bf0)\n + t1700: make sure split-index respects core.sharedrepository\n + t1301: move modebits() to test-lib-functions.sh\n + read-cache: use shared perms when writing shared index\n\n The split index code did not honor core.sharedrepository setting\n correctly.\n\n Will merge to 'master'.\n\n\n* ex/deprecate-empty-pathspec-as-match-all (2017-06-23) 2 commits\n  (merged to 'next' on 2017-06-26 at d026281517)\n + pathspec: die on empty strings as pathspec\n + t0027: do not use an empty string as a pathspec element\n\n The final step to make an empty string as a pathspec element\n illegal.  We started this by first deprecating and warning a\n pathspec that has such an element in 2.11 (Nov 2016).\n\n Hopefully we can merge this down to the 'master' by the end of the\n year?  A deprecation warning period that is about 1 year does not\n sound too bad.\n\n Will cook in 'next'.\n\n\n* sb/pull-rebase-submodule (2017-06-27) 4 commits\n - builtin/fetch cleanup: always set default value for submodule recursing\n - pull: optionally rebase submodules (remote submodule changes only)\n - builtin/fetch: parse recurse-submodules-default at default options parsing\n - builtin/fetch: factor submodule recurse parsing out to submodule config\n\n \"git pull --rebase --recurse-submodules\" learns to rebase the\n branch in the submodules to an updated base.\n\n\n* bw/repo-object (2017-06-23) 21 commits\n  (merged to 'next' on 2017-06-26 at ed9c0b77c3)\n + ls-files: use repository object\n + repository: enable initialization of submodules\n + submodule: convert is_submodule_initialized to work on a repository\n + submodule: add repo_read_gitmodules\n + submodule-config: store the_submodule_cache in the_repository\n + repository: add index_state to struct repo\n + config: read config from a repository object\n + path: add repo_worktree_path and strbuf_repo_worktree_path\n + path: add repo_git_path and strbuf_repo_git_path\n + path: worktree_git_path() should not use file relocation\n + path: convert do_git_path to take a 'struct repository'\n + path: convert strbuf_git_common_path to take a 'struct repository'\n + path: always pass in commondir to update_common_dir\n + path: create path.h\n + environment: store worktree in the_repository\n + environment: place key repository state in the_repository\n + repository: introduce the repository object\n + environment: remove namespace_len variable\n + setup: add comment indicating a hack\n + setup: don't perform lazy initialization of repository state\n + Merge branches 'bw/ls-files-sans-the-index' and 'bw/config-h' into bw/repo-object\n\n Introduce a \"repository\" object to eventually make it easier to\n work in multiple repositories (the primary focus is to work with\n the superproject and its submodules) in a single process.\n\n Will merge to 'master'.\n\n\n* pw/unquote-path-in-git-pm (2017-06-30) 4 commits\n - t9700: add tests for Git::unquote_path()\n - Git::unquote_path(): throw an exception on bad path\n - Git::unquote_path(): handle '\\a'\n - add -i: move unquote_path() to Git.pm\n\n Code refactoring.\n\n Will merge to 'next'.\n\n\n* rs/sha1-name-readdir-optim (2017-06-24) 4 commits\n  (merged to 'next' on 2017-06-26 at a70587f2b9)\n + sha1_file: guard against invalid loose subdirectory numbers\n + sha1_file: let for_each_file_in_obj_subdir() handle subdir names\n + p4205: add perf test script for pretty log formats\n + sha1_name: cache readdir(3) results in find_short_object_filename()\n\n Optimize \"what are the object names already taken in an alternate\n object database?\" query that is used to derive the length of prefix\n an object name is uniquely abbreviated to.\n\n Will merge to 'master'.\n\n\n* jt/unify-object-info (2017-06-26) 8 commits\n  (merged to 'next' on 2017-06-26 at 540ea81983)\n + sha1_file: refactor has_sha1_file_with_flags\n + sha1_file: do not access pack if unneeded\n + sha1_file: teach sha1_object_info_extended more flags\n + sha1_file: refactor read_object\n + sha1_file: move delta base cache code up\n + sha1_file: rename LOOKUP_REPLACE_OBJECT\n + sha1_file: rename LOOKUP_UNKNOWN_OBJECT\n + sha1_file: teach packed_object_info about typename\n\n Code clean-ups.\n\n Will merge to 'master'.\n\n\n* mh/packed-ref-store (2017-06-23) 29 commits\n - read_packed_refs(): die if `packed-refs` contains bogus data\n - repack_without_refs(): don't lock or unlock the packed refs\n - commit_packed_refs(): remove call to `packed_refs_unlock()`\n - clear_packed_ref_cache(): don't protest if the lock is held\n - packed_refs_unlock(), packed_refs_is_locked(): new functions\n - packed_refs_lock(): report errors via a `struct strbuf *err`\n - packed_refs_lock(): function renamed from lock_packed_refs()\n - commit_packed_refs(): use a staging file separate from the lockfile\n - commit_packed_refs(): report errors rather than dying\n - packed_ref_store: make class into a subclass of `ref_store`\n - packed-backend: new module for handling packed references\n - packed_read_raw_ref(): new function, replacing `resolve_packed_ref()`\n - packed_ref_store: support iteration\n - packed_peel_ref(): new function, extracted from `files_peel_ref()`\n - repack_without_refs(): take a `packed_ref_store *` parameter\n - get_packed_ref(): take a `packed_ref_store *` parameter\n - rollback_packed_refs(): take a `packed_ref_store *` parameter\n - commit_packed_refs(): take a `packed_ref_store *` parameter\n - lock_packed_refs(): take a `packed_ref_store *` parameter\n - add_packed_ref(): take a `packed_ref_store *` parameter\n - get_packed_refs(): take a `packed_ref_store *` parameter\n - get_packed_ref_cache(): take a `packed_ref_store *` parameter\n - validate_packed_ref_cache(): take a `packed_ref_store *` parameter\n - clear_packed_ref_cache(): take a `packed_ref_store *` parameter\n - packed_ref_store: move `packed_refs_lock` member here\n - packed_ref_store: move `packed_refs_path` here\n - packed_ref_store: new struct\n - add_packed_ref(): teach function to overwrite existing refs\n - t1408: add a test of stale packed refs covered by loose refs\n\n The \"ref-store\" code reorganization continues.\n\n Is this now ready for 'next'?\n\n\n* sb/submodule-doc (2017-06-22) 1 commit\n - submodules: overhaul documentation\n\n Doc update.\n\n Waiting for discussion to settle.\n\n\n* sd/branch-copy (2017-06-18) 3 commits\n - branch: add a --copy (-c) option to go with --move (-m)\n - branch: add test for -m renaming multiple config sections\n - config: create a function to format section headers\n\n \"git branch\" learned \"-c/-C\" to create and switch to a new branch\n by copying an existing one.\n\n Has a bit of interaction with mh/packed-ref-store and bw/config-h,\n so perhaps needs to wait for the former to stabilize a bit more\n and possibly rebasing on them.\n\n\n* ls/filter-process-delayed (2017-06-30) 7 commits\n - convert: add \"status=delayed\" to filter process protocol\n - convert: refactor capabilities negotiation\n - convert: move multiple file filter error handling to separate function\n - convert: put the flags field before the flag itself for consistent style\n - t0021: write \"OUT <size>\" only on success\n - t0021: make debug log file name configurable\n - t0021: keep filter log files on comparison\n\n The filter-process interface learned to allow a process with long\n latency give a \"delayed\" response.\n\n Will merge to 'next'.\n\n\n* ab/sha1dc (2017-06-27) 3 commits\n - sha1collisiondetection: automatically enable when submodule is populated\n - sha1dc: optionally use sha1collisiondetection as a submodule\n - sha1dc: correct endian detection for Solaris (and others?)\n\n The \"collission-detecting\" implementation of SHA-1 hash we borrowed\n from is replaced by directly binding the upstream project as our\n submodule.  Glitches on minority platforms are still being worked out.\n\n Will keep in 'pu'.\n\n\n* bp/fsmonitor (2017-06-12) 6 commits\n - fsmonitor: add a sample query-fsmonitor hook script for Watchman\n - fsmonitor: add documentation for the fsmonitor extension.\n - fsmonitor: add test cases for fsmonitor extension\n - fsmonitor: teach git to optionally utilize a file system monitor to speed up detecting new or changed files.\n - dir: make lookup_untracked() available outside of dir.c\n - bswap: add 64 bit endianness helper get_be64\n\n We learned to talk to watchman to speed up \"git status\".\n\n No more comments or updates?\n\n\n* sb/diff-color-move (2017-06-30) 26 commits\n - diff: document the new --color-moved setting\n - diff.c: add dimming to moved line detection\n - diff.c: color moved lines differently, plain mode\n - diff.c: color moved lines differently\n - diff.c: buffer all output if asked to\n - diff.c: emit_diff_symbol learns about DIFF_SYMBOL_SUMMARY\n - diff.c: emit_diff_symbol learns about DIFF_SYMBOL_STAT_SEP\n - diff.c: convert word diffing to use emit_diff_symbol\n - diff.c: convert show_stats to use emit_diff_symbol\n - diff.c: convert emit_binary_diff_body to use emit_diff_symbol\n - submodule.c: migrate diff output to use emit_diff_symbol\n - diff.c: emit_diff_symbol learns DIFF_SYMBOL_REWRITE_DIFF\n - diff.c: emit_diff_symbol learns about DIFF_SYMBOL_BINARY_FILES\n - diff.c: emit_diff_symbol learns DIFF_SYMBOL_HEADER\n - diff.c: emit_diff_symbol learns DIFF_SYMBOL_FILEPAIR_{PLUS, MINUS}\n - diff.c: emit_diff_symbol learns DIFF_SYMBOL_CONTEXT_INCOMPLETE\n - diff.c: emit_diff_symbol learns DIFF_SYMBOL_WORDS[_PORCELAIN]\n - diff.c: migrate emit_line_checked to use emit_diff_symbol\n - diff.c: emit_diff_symbol learns DIFF_SYMBOL_NO_LF_EOF\n - diff.c: emit_diff_symbol learns DIFF_SYMBOL_CONTEXT_FRAGINFO\n - diff.c: emit_diff_symbol learns DIFF_SYMBOL_CONTEXT_MARKER\n - diff.c: introduce emit_diff_symbol\n - diff.c: factor out diff_flush_patch_all_file_pairs\n - diff.c: move line ending check into emit_hunk_header\n - diff.c: readability fix\n - Merge branch 'sb/hashmap-customize-comparison' into sb/diff-color-move\n (this branch uses sb/hashmap-customize-comparison.)\n\n \"git diff\" has been taught to optionally paint new lines that are\n the same as deleted lines elsewhere differently from genuinely new\n lines.\n\n Looking good.\n cf. <CAGZ79kaK00CpXOtXnx_u7_KHbZq4Mz8vWHKy2a8p1gQ8ogE-OA@mail.gmail.com>\n\n--------------------------------------------------\n[Discarded]\n\n* mh/packed-ref-store-prep-extra (2017-06-18) 1 commit\n . prefix_ref_iterator_advance(): relax the check of trim length\n\n Split out of mh/packed-ref-store-prep.\n\n\n* nd/prune-in-worktree (2017-04-24) 12 commits\n . rev-list: expose and document --single-worktree\n . revision.c: --reflog add HEAD reflog from all worktrees\n . files-backend: make reflog iterator go through per-worktree reflog\n . revision.c: --all adds HEAD from all worktrees\n . refs: remove dead for_each_*_submodule()\n . revision.c: use refs_for_each*() instead of for_each_*_submodule()\n . refs: add refs_head_ref()\n . refs: move submodule slash stripping code to get_submodule_ref_store\n . refs.c: refactor get_submodule_ref_store(), share common free block\n . revision.c: --indexed-objects add objects from all worktrees\n . revision.c: refactor add_index_objects_to_pending()\n . revision.h: new flag in struct rev_info wrt. worktree-related refs\n\n \"git gc\" and friends when multiple worktrees are used off of a\n single repository did not consider the index and per-worktree refs\n of other worktrees as the root for reachability traversal, making\n objects that are in use only in other worktrees to be subject to\n garbage collection.\n\n\n* ab/free-and-null (2017-06-28) 2 commits\n  (merged to 'next' on 2017-06-28 at 1cf373c61a)\n + Revert \"coccinelle: add a rule to make \"expression\" code use FREE_AND_NULL()\"\n  (merged to 'next' on 2017-06-28 at 1785f88122)\n + coccinelle: add a rule to make \"expression\" code use FREE_AND_NULL()\n\n The coccinelle rule for free-and-null refactoring got simplified.\n"},{"id":"323668","messageId":"87podkehcx.fsf@gmail.com","threadId":"46299","inReplyTo":"xmqqk23tp2jk.fsf@gitster.mtv.corp.google.com","subject":"Re: What's cooking in git.git (Jun 2017, #09; Fri, 30)","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2017-07-01T07:39:10Z","receivedAt":"2017-07-01T07:39:26Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"\nOn Fri, Jun 30 2017, Junio C. Hamano jotted:\n\n> * xz/send-email-batch-size (2017-05-23) 1 commit\n>  - send-email: --batch-size to work around some SMTP server limit\n>\n>  \"git send-email\" learned to overcome some SMTP server limitation\n>  that does not allow many pieces of e-mails to be sent over a single\n>  session.\n>\n>  Waiting for a response.\n>  cf. <CACBZZX5GYV50rjg9X602JHqFPaoofH9TwDf_-r_MDu8-rmNV6Q@mail.gmail.com>\n>  cf. <xmqqo9tfff2w.fsf@gitster.mtv.corp.google.com>\n>\n>  \"\"\"I thought your wish (which I found reasonable) was to record\n>  whatever information that would help us in the future in the log\n>  message?  I was waiting for that to happen.\"\"\"\n\nI think it's fine in lieu of xiaoqiang zhao not being responsive to just\nmerge this as-is. The info that can help us in the future is in the ML\narchive, which should be good enough.\n\n> * ab/strbuf-addftime-tzname-boolify (2017-06-24) 3 commits\n>  - REWORD ONLY SQUASH\n>  - strbuf: change an always NULL/\"\" strbuf_addftime() param to bool\n>  - strbuf.h comment: discuss strbuf_addftime() arguments in order\n>\n>  strbuf_addftime() is further getting tweaked.\n>\n>  Waiting for a response.\n>  cf. <xmqqk2419rhg.fsf@gitster.mtv.corp.google.com>\n\nMeant to get to this after the last \"What's Cooking\", will submit\nanother version soon.\n\n> * ab/wildmatch (2017-06-23) 1 commit\n>  - wildmatch: remove unused wildopts parameter\n>\n>  Prepare the wildmatch API for future enhancements to allow a\n>  pattern that is repeatedly matched against many strings to be\n>  precompiled.\n\n[...]\n\n> * ex/deprecate-empty-pathspec-as-match-all (2017-06-23) 2 commits\n>   (merged to 'next' on 2017-06-26 at d026281517)\n>  + pathspec: die on empty strings as pathspec\n>  + t0027: do not use an empty string as a pathspec element\n>\n>  The final step to make an empty string as a pathspec element\n>  illegal.  We started this by first deprecating and warning a\n>  pathspec that has such an element in 2.11 (Nov 2016).\n>\n>  Hopefully we can merge this down to the 'master' by the end of the\n>  year?  A deprecation warning period that is about 1 year does not\n>  sound too bad.\n>\n>  Will cook in 'next'.\n\nI have a longer patch series involving the \"wildmatch: remove unused\nwildopts parameter\" patch (although not conflicting with it) which\nassumes:\n\n 1. We'll merge down my \"wildmatch: remove unused wildopts parameter\" to\n    master (doesn't conflict with #3).\n\n 2. This ex/deprecate-empty-pathspec-as-match-all series will get in\n\n 3. My series, which among other things cleans up the wildmatch tests a\n    lot (and adds that new wildmatch pre-compile API that was ejected)\n    could be reviewed & merged down.\n\nThe reason I'm waiting on #3 is because one of the things I'm doing is\nimproving the wildmatch tests to not only test via calling raw\nwildmatch(), but also roundtripping via git-ls-files, and this will\nconflict in a very minor way with #2 (the test will need to be changed\nfrom \"this warns + works differently\" -> \"this dies + doesn't work\").\n\nBut if #2 is something that's going to cook until the end of the year\nI'm going to submit this sooner, and then we can just handle the minor\nconflict. Is cooking it for that long really the plan?\n\nAlso, here's a minor RFC, as part of that series I need to create files\n/ directories for each of the tests now in the wildmatch tests, this\ninvolves creating files like \"?a?b\", \"a[]b\", \"$\" etc. I.e. this won't\nwork on all platforms.\n\nSo my WIP is, and I'd like feedback on the viability of the general approach:\n\n    create_test_file() {\n    \tfile=$1\n\n    \t# `touch .` will succeed but obviously not do what we intend\n    \t# here.\n    \ttest \"$file\" = \".\" && return 1\n    \t# We cannot create a file with an empty filename.\n    \ttest \"$file\" = \"\" && return 1\n    \t# The tests that are testing that e.g. foo//bar is matched by\n    \t# foo/*/bar can't be tested on filesystems since there's no\n    \t# way we're getting a double slash.\n    \techo \"$file\" | grep -F '//' && return 1\n\n    \tdirs=$(echo \"$file\" | sed -r 's!/[^/]+$!!')\n\n    \t# We touch \"./$file\" instead of \"$file\" because even an\n    \t# escaped \"touch -- -\" means something different.\n    \tif test \"$file\" != \"$dirs\"\n    \tthen\n    \t\tmkdir -p -- \"$dirs\" 2>/dev/null &&\n    \t\ttouch -- \"./$file\" 2>/dev/null &&\n    \t\treturn 0\n    \telse\n    \t\ttouch -- \"./$file\" 2>/dev/null &&\n    \t\treturn 0\n    \tfi\n    \treturn 1\n    }\n\nAnd then later on for the tests I do:\n\n\t# The existing test\n\ttest_expect_success \"wildmatch:     match '$text' '$pattern'\" \"\n\t\ttest-wildmatch wildmatch '$text' '$pattern'\n\t\"\n\n\t# My new test\n\tif create_test_file \"$text\"\n\tthen\n\t\ttest_expect_success \"wildmatch(ls): match '$pattern' '$text'\" \"\n\t\t\ttest_when_finished \\\"\n\t\t\t\trm -rf -- * &&\n\t\t\t\tgit reset\n\t\t\t\\\" &&\n\t\t\tgit add -A &&\n\t\t\t>expect.err &&\n\t\t\tprintf '%s' '$text' >expect &&\n\t\t\tgit --glob-pathspecs ls-files -z -- '$pattern' 2>actual.err | tr -d '\\0' >actual &&\n\t\t\ttest_cmp expect.err actual.err &&\n\t\t\ttest_cmp expect actual\n\t\t\"\n\telse\n\t\ttest_expect_failure \"wildmatch(ls): match skip '$pattern' '$text'\" 'false'\n\tfi\n\nThis still needs to be cleaned up a bit to be parameterized (i.e. the\n--glob-pathspecs argument, whether it should error etc.).\n\nIt works for me on Linux, but I'm wondering if others see any issues\nwith the approach, does simply trying to create bizarro filenames on\nsome OSs cause issues? I don't think so, but let's make sure.\n\nAlso this whole if/else with test_expect_success/test_expect_failure\npattern kind of sucks, I'm thinking of adding:\n\n    # Do the create_test_file() test to see if we can create the file then:\n    SKIP_TEST=<explanation if create_test_file() returned non-zero, empty string otherwise>\n    test_expect_success '...' '...'\n\nI.e. to add a facility to test-lib.sh to be picked up by test_skip to\nset a variable to skip individual tests with an explanation, currently\nwe have no non-hacky way to do this with the test-lib. I.e. the\nequivalent of Test::More:\n\n    $ perl -MTest::More=no_plan -wE 'my $test = \"Match bizarro glob on fs\"; if (shift) { pass $test } else { SKIP: { skip $test } }' 0\n    ok 1 # skip Match bizarro glob on fs\n    1..1\n    $ perl -MTest::More=no_plan -wE 'my $test = \"Match bizarro glob on fs\"; if (shift) { pass $test } else { SKIP: { skip $test } }' 1\n    ok 1 - Match bizarro glob on fs\n    1..1\n\nThe \"# skip\" is magical and will be picked up as skip TAP.\n\nWe could also as a hack do:\n\n    diff --git a/t/test-lib.sh b/t/test-lib.sh\n    index 2306574dc9..0cea1711c2 100644\n    --- a/t/test-lib.sh\n    +++ b/t/test-lib.sh\n    @@ -398,7 +398,12 @@ trap 'exit $?' INT\n\n     test_ok_ () {\n            test_success=$(($test_success + 1))\n    -       say_color \"\" \"ok $test_count - $@\"\n    +       if echo \"$@\" | grep -q '^# skip'\n    +       then\n    +               say_color \"\" \"ok $test_count $@\"\n    +       else\n    +               say_color \"\" \"ok $test_count - $@\"\n    +       fi\n     }\n\n     test_failure_ () {\n\nThis would avoid the caveats of setting a possible persistent shell\nvariable, but OTOH the code would become quite ugly, you'd need:\n\n    if <skip>\n    then\n        test_expect_success '# skip <reason>' 'true'\n    else\n        test_expect_success '<real test>' '<real code>'\n    fi\n\nSo I'm heavily leaning towards just adding a $SKIP_TEST variable of some\nsort.\n\n> * ab/sha1dc (2017-06-27) 3 commits\n>  - sha1collisiondetection: automatically enable when submodule is populated\n>  - sha1dc: optionally use sha1collisiondetection as a submodule\n>  - sha1dc: correct endian detection for Solaris (and others?)\n>\n>  The \"collission-detecting\" implementation of SHA-1 hash we borrowed\n>  from is replaced by directly binding the upstream project as our\n>  submodule.  Glitches on minority platforms are still being worked out.\n>\n>  Will keep in 'pu'.\n\nThe status of this is that we've come to a consensus with upstream /\nanother reported about what to do about this issue in\nhttps://github.com/cr-marcstevens/sha1collisiondetection/pull/34 but\npull request was a bit of a mess (multiple merges etc). I rebased &\ncleaned that up this morning as\nhttps://github.com/cr-marcstevens/sha1collisiondetection/pull/37\n\nI'll wait for that to get into upstream before submitting a new round of\nthis.\n"},{"id":"323677","messageId":"f1dc9bc2-b1ad-ad28-cfbb-ab55aa302e4f@web.de","threadId":"46299","inReplyTo":"87podkehcx.fsf@gmail.com","subject":"Re: What's cooking in git.git (Jun 2017, #09; Fri, 30)","fromName":"Torsten Bögershausen","fromEmail":"tboegi@web.de","sentAt":"2017-07-01T12:59:02Z","receivedAt":"2017-07-01T12:59:26Z","isPatch":false,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"\n\nOn 01/07/17 09:39, Ævar Arnfjörð Bjarmason wrote:\n> \n> On Fri, Jun 30 2017, Junio C. Hamano jotted:\n> \n>> * xz/send-email-batch-size (2017-05-23) 1 commit\n>>   - send-email: --batch-size to work around some SMTP server limit\n>>\n>>   \"git send-email\" learned to overcome some SMTP server limitation\n>>   that does not allow many pieces of e-mails to be sent over a single\n>>   session.\n>>\n>>   Waiting for a response.\n>>   cf. <CACBZZX5GYV50rjg9X602JHqFPaoofH9TwDf_-r_MDu8-rmNV6Q@mail.gmail.com>\n>>   cf. <xmqqo9tfff2w.fsf@gitster.mtv.corp.google.com>\n>>\n>>   \"\"\"I thought your wish (which I found reasonable) was to record\n>>   whatever information that would help us in the future in the log\n>>   message?  I was waiting for that to happen.\"\"\"\n> \n> I think it's fine in lieu of xiaoqiang zhao not being responsive to just\n> merge this as-is. The info that can help us in the future is in the ML\n> archive, which should be good enough.\n> \n>> * ab/strbuf-addftime-tzname-boolify (2017-06-24) 3 commits\n>>   - REWORD ONLY SQUASH\n>>   - strbuf: change an always NULL/\"\" strbuf_addftime() param to bool\n>>   - strbuf.h comment: discuss strbuf_addftime() arguments in order\n>>\n>>   strbuf_addftime() is further getting tweaked.\n>>\n>>   Waiting for a response.\n>>   cf. <xmqqk2419rhg.fsf@gitster.mtv.corp.google.com>\n> \n> Meant to get to this after the last \"What's Cooking\", will submit\n> another version soon.\n> \n>> * ab/wildmatch (2017-06-23) 1 commit\n>>   - wildmatch: remove unused wildopts parameter\n>>\n>>   Prepare the wildmatch API for future enhancements to allow a\n>>   pattern that is repeatedly matched against many strings to be\n>>   precompiled.\n> \n> [...]\n> \n>> * ex/deprecate-empty-pathspec-as-match-all (2017-06-23) 2 commits\n>>    (merged to 'next' on 2017-06-26 at d026281517)\n>>   + pathspec: die on empty strings as pathspec\n>>   + t0027: do not use an empty string as a pathspec element\n>>\n>>   The final step to make an empty string as a pathspec element\n>>   illegal.  We started this by first deprecating and warning a\n>>   pathspec that has such an element in 2.11 (Nov 2016).\n>>\n>>   Hopefully we can merge this down to the 'master' by the end of the\n>>   year?  A deprecation warning period that is about 1 year does not\n>>   sound too bad.\n>>\n>>   Will cook in 'next'.\n> \n> I have a longer patch series involving the \"wildmatch: remove unused\n> wildopts parameter\" patch (although not conflicting with it) which\n> assumes:\n> \n>   1. We'll merge down my \"wildmatch: remove unused wildopts parameter\" to\n>      master (doesn't conflict with #3).\n> \n>   2. This ex/deprecate-empty-pathspec-as-match-all series will get in\n> \n>   3. My series, which among other things cleans up the wildmatch tests a\n>      lot (and adds that new wildmatch pre-compile API that was ejected)\n>      could be reviewed & merged down.\n> \n> The reason I'm waiting on #3 is because one of the things I'm doing is\n> improving the wildmatch tests to not only test via calling raw\n> wildmatch(), but also roundtripping via git-ls-files, and this will\n> conflict in a very minor way with #2 (the test will need to be changed\n> from \"this warns + works differently\" -> \"this dies + doesn't work\").\n> \n> But if #2 is something that's going to cook until the end of the year\n> I'm going to submit this sooner, and then we can just handle the minor\n> conflict. Is cooking it for that long really the plan?\n> \n> Also, here's a minor RFC, as part of that series I need to create files\n> / directories for each of the tests now in the wildmatch tests, this\n> involves creating files like \"?a?b\", \"a[]b\", \"$\" etc. I.e. this won't\n> work on all platforms.\n> \n> So my WIP is, and I'd like feedback on the viability of the general approach:\n> \n>      create_test_file() {\n>      \tfile=$1\n> \n>      \t# `touch .` will succeed but obviously not do what we intend\n>      \t# here.\n>      \ttest \"$file\" = \".\" && return 1\n>      \t# We cannot create a file with an empty filename.\n>      \ttest \"$file\" = \"\" && return 1\n>      \t# The tests that are testing that e.g. foo//bar is matched by\n>      \t# foo/*/bar can't be tested on filesystems since there's no\n>      \t# way we're getting a double slash.\n>      \techo \"$file\" | grep -F '//' && return 1\n> \n>      \tdirs=$(echo \"$file\" | sed -r 's!/[^/]+$!!')\n\nsed -r is a GNU extension, isn't it ?\nhttp://pubs.opengroup.org/onlinepubs/7908799/xcu/sed.html\n\nThis may work:\nsed -e 's!/[^/][^/]*$!!')\n\n\n(The rest looks good - at first glance)\n"},{"id":"323744","messageId":"4374FA169AD7465AA39BDB477A348B02@PhilipOakley","threadId":"46299","inReplyTo":"xmqqk23tp2jk.fsf@gitster.mtv.corp.google.com","subject":"Re: What's cooking in git.git (Jun 2017, #09; Fri, 30)","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.org","sentAt":"2017-07-02T14:26:02Z","receivedAt":"2017-07-02T14:26:06Z","isPatch":false,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"From: \"Junio C Hamano\" <gitster@pobox.com>\n> 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\n> the integration branches, but I am still holding onto them.\n>\n\nJunio,\nIs it possible to include a table of contents that lists the integration \nbranches, split by your categories, to help find areas of interest?\n\n[Graduated to \"master\"]\n* topic list\n[New Topics]\n[Stalled]\n[Cooking]\n[Discarded]\n\nThe TOC wouldn't need the [] or * markings if that's a problem.\n--\nPhilip\n\n\n> You can find the changes described here in the integration branches\n> of the repositories listed at\n>\n>    http://git-blame.blogspot.com/p/git-public-repositories.html\n>\n> --------------------------------------------------\n> [Graduated to \"master\"]\n>\n> * ab/die-errors-in-threaded (2017-06-21) 1 commit\n<snip> \n\n"},{"id":"323758","messageId":"xmqqo9t1l6vi.fsf@gitster.mtv.corp.google.com","threadId":"46299","inReplyTo":"4374FA169AD7465AA39BDB477A348B02@PhilipOakley","subject":"Re: What's cooking in git.git (Jun 2017, #09; Fri, 30)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2017-07-03T18:20:33Z","receivedAt":"2017-07-03T18:20:40Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Philip Oakley\" <philipoakley@iee.org> writes:\n\n> Junio,\n> Is it possible to include a table of contents that lists the\n> integration branches, split by your categories, to help find areas of\n> interest?\n>\n> [Graduated to \"master\"]\n> * topic list\n> [New Topics]\n> [Stalled]\n> [Cooking]\n> [Discarded]\n>\n> The TOC wouldn't need the [] or * markings if that's a problem.\n\nI am not sure what you are asking.  Is this the command you are\nlooking for?\n\n $ grep -e \"^[[*]\" whats-cooking.txt\n\n"},{"id":"323772","messageId":"C31723137B784D54A3CDB1B7D9432D7E@PhilipOakley","threadId":"46299","inReplyTo":"xmqqo9t1l6vi.fsf@gitster.mtv.corp.google.com","subject":"Re: What's cooking in git.git (Jun 2017, #09; Fri, 30)","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.org","sentAt":"2017-07-03T19:13:02Z","receivedAt":"2017-07-03T19:13:12Z","isPatch":false,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"From: \"Junio C Hamano\" <gitster@pobox.com>\n> \"Philip Oakley\" <philipoakley@iee.org> writes:\n>\n>> Junio,\n>> Is it possible to include a table of contents that lists the\n>> integration branches, split by your categories, to help find areas of\n>> interest?\n>>\n>> [Graduated to \"master\"]\n>> * topic list\n>> [New Topics]\n>> [Stalled]\n>> [Cooking]\n>> [Discarded]\n>>\n>> The TOC wouldn't need the [] or * markings if that's a problem.\n>\n> I am not sure what you are asking.  Is this the command you are\n> looking for?\n>\n> $ grep -e \"^[[*]\" whats-cooking.txt\n>\nAh, thanks.\n\nIt does presume that one has extracted the email to the text file, which is \neasier on some systems and mail clients than others ;-)\nAm I right that the What's cooking  is prepared by a script?\n--\nPhilip \n\n"},{"id":"323774","messageId":"xmqqfuedl1ct.fsf@gitster.mtv.corp.google.com","threadId":"46299","inReplyTo":"C31723137B784D54A3CDB1B7D9432D7E@PhilipOakley","subject":"Re: What's cooking in git.git (Jun 2017, #09; Fri, 30)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2017-07-03T20:19:46Z","receivedAt":"2017-07-03T20:19:53Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Philip Oakley\" <philipoakley@iee.org> writes:\n\n> Am I right that the What's cooking  is prepared by a script?\n\nBecause I have to keep track of so many topics, its maintenance is\nheavily helped by a script. I do not think it is sensible to expect\nme to (or it would be good use of my time) correctly update the list\nof commits manually every time a topic is replaced with its new\nversion.\n\nBut I consider the use of the script just like my use of Emacs to\nedit the final end result.  Yes, I use tools to prepare it, and the\ntools know certain rules that I prefer to apply to the document,\nsuch as \"a topic that has not been touched since the previous issue\nby default does not need its description updated.\"\n\nDoes that answer your question?\n\n"},{"id":"323793","messageId":"xmqq8tk4loyr.fsf@gitster.mtv.corp.google.com","threadId":"46299","inReplyTo":"C31723137B784D54A3CDB1B7D9432D7E@PhilipOakley","subject":"Re: What's cooking in git.git (Jun 2017, #09; Fri, 30)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2017-07-04T06:02:04Z","receivedAt":"2017-07-04T06:02:14Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Philip Oakley\" <philipoakley@iee.org> writes:\n\n> From: \"Junio C Hamano\" <gitster@pobox.com>\n>\n>> I am not sure what you are asking.  Is this the command you are\n>> looking for?\n>>\n>> $ grep -e \"^[[*]\" whats-cooking.txt\n>>\n> Ah, thanks.\n>\n> It does presume that one has extracted the email to the text file,\n> which is easier on some systems and mail clients than others ;-)\n\nPerhaps you would want to find an e-mail client that can handle text\nfiles better, then? ;-)\n\nIf you are cloning and following along my tree from one of these\nplaces:\n\n    git://repo.or.cz/alt-git.git/\n    git://git.kernel.org/pub/scm/git/git.git/\n    git://github.com/git/git.git/\n\nthe 'todo' branch in these repositories keeps track of the\nwhats-cooking.txt report (among other things), so you can also:\n\n    $ git cat-file -p origin/todo:whats-cooking.txt |\n      grep -e \"^[[*]\"\n\nto get the same effect.\n\n\n\n\n"},{"id":"323813","messageId":"CAGZ79karazektmWg0nneYnfGU29dm8BtPUndOCobetH4xSy=tg@mail.gmail.com","threadId":"46299","inReplyTo":"xmqq8tk4loyr.fsf@gitster.mtv.corp.google.com","subject":"Re: What's cooking in git.git (Jun 2017, #09; Fri, 30)","fromName":"Stefan Beller","fromEmail":"sbeller@google.com","sentAt":"2017-07-05T00:17:28Z","receivedAt":"2017-07-05T00:17:35Z","isPatch":false,"sender":{"key":"stefanbeller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/455868?v=4"},"body":"On Mon, Jul 3, 2017 at 11:02 PM, Junio C Hamano <gitster@pobox.com> wrote:\n> \"Philip Oakley\" <philipoakley@iee.org> writes:\n>\n>> From: \"Junio C Hamano\" <gitster@pobox.com>\n>>\n>>> I am not sure what you are asking.  Is this the command you are\n>>> looking for?\n>>>\n>>> $ grep -e \"^[[*]\" whats-cooking.txt\n>>>\n>> Ah, thanks.\n>>\n>> It does presume that one has extracted the email to the text file,\n>> which is easier on some systems and mail clients than others ;-)\n>\n> Perhaps you would want to find an e-mail client that can handle text\n> files better, then? ;-)\n>\n> If you are cloning and following along my tree from one of these\n> places:\n>\n>     git://repo.or.cz/alt-git.git/\n>     git://git.kernel.org/pub/scm/git/git.git/\n>     git://github.com/git/git.git/\n>\n> the 'todo' branch in these repositories keeps track of the\n> whats-cooking.txt report (among other things), so you can also:\n>\n>     $ git cat-file -p origin/todo:whats-cooking.txt |\n>       grep -e \"^[[*]\"\n>\n> to get the same effect.\n>\n\nFWIW:\nI have a script in my git dir,\n\ncat git/cookreport.sh\ngit -C Meta pull origin todo\nMeta/cook -w\n\nwith Meta being a repo tracking one of the URLs above.\n\nI might add  a | grep -e \"^[[*]\" or add some scripting to verbose\nreport my own topics.\n\nThanks,\nStefan\n"},{"id":"323820","messageId":"DEBF0737E2B74FC89FF1C4E4DB8AC45B@PhilipOakley","threadId":"46299","inReplyTo":"xmqqfuedl1ct.fsf@gitster.mtv.corp.google.com","subject":"Re: What's cooking in git.git (Jun 2017, #09; Fri, 30)","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.org","sentAt":"2017-07-05T07:30:35Z","receivedAt":"2017-07-05T07:30:42Z","isPatch":false,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"From: \"Junio C Hamano\" <gitster@pobox.com>\nSent: Monday, July 03, 2017 9:19 PM\n> \"Philip Oakley\" <philipoakley@iee.org> writes:\n>\n>> Am I right that the What's cooking  is prepared by a script?\n>\n> Because I have to keep track of so many topics, its maintenance is\n> heavily helped by a script. I do not think it is sensible to expect\n> me to (or it would be good use of my time) correctly update the list\n> of commits manually every time a topic is replaced with its new\n> version.\n>\nDefinately. I was hoping that a 'contents list' element (at the point of \nsending the emails) could also be part of the automated scripting.\n\n> But I consider the use of the script just like my use of Emacs to\n> edit the final end result.  Yes, I use tools to prepare it, and the\n> tools know certain rules that I prefer to apply to the document,\n> such as \"a topic that has not been touched since the previous issue\n> by default does not need its description updated.\"\n>\n> Does that answer your question?\n>\nI see the script's location is given in a follow up response. I'll see what \nopportunities for a TOC there may be within the flow, though my local todo \nlist is getting a bit long with other personal matters.\n--\nPhilip \n\n"},{"id":"323838","messageId":"xmqq60f6kg5m.fsf@gitster.mtv.corp.google.com","threadId":"46299","inReplyTo":"87podkehcx.fsf@gmail.com","subject":"Re: What's cooking in git.git (Jun 2017, #09; Fri, 30)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2017-07-05T16:22:13Z","receivedAt":"2017-07-05T16:22:30Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:\n\n> On Fri, Jun 30 2017, Junio C. Hamano jotted:\n>\n>> * xz/send-email-batch-size (2017-05-23) 1 commit\n>>  - send-email: --batch-size to work around some SMTP server limit\n>>\n>>  \"git send-email\" learned to overcome some SMTP server limitation\n>>  that does not allow many pieces of e-mails to be sent over a single\n>>  session.\n>>\n>>  Waiting for a response.\n>>  cf. <CACBZZX5GYV50rjg9X602JHqFPaoofH9TwDf_-r_MDu8-rmNV6Q@mail.gmail.com>\n>>  cf. <xmqqo9tfff2w.fsf@gitster.mtv.corp.google.com>\n>>\n>>  \"\"\"I thought your wish (which I found reasonable) was to record\n>>  whatever information that would help us in the future in the log\n>>  message?  I was waiting for that to happen.\"\"\"\n>\n> I think it's fine in lieu of xiaoqiang zhao not being responsive to just\n> merge this as-is. The info that can help us in the future is in the ML\n> archive, which should be good enough.\n\nOK.  I'll amend to add a few lines of note to the commit log and\nthen merge it down.\n\n> So my WIP is, and I'd like feedback on the viability of the general approach:\n>\n>     create_test_file() {\n>     \tfile=$1\n>\n>     \t# `touch .` will succeed but obviously not do what we intend\n>     \t# here.\n\nIf you want to create, do not use \"touch\" that gives readers a false\nand confusing impression that you care about the timestamp of the\nthing being updated.  If you say \">./$file\", you can get an error from\nthe shell just fine, I think.\n\n>     \ttest \"$file\" = \".\" && return 1\n>     \t# We cannot create a file with an empty filename.\n>     \ttest \"$file\" = \"\" && return 1\n\nLikewise, as that would become \">./\".\n\n>     \t# The tests that are testing that e.g. foo//bar is matched by\n>     \t# foo/*/bar can't be tested on filesystems since there's no\n>     \t# way we're getting a double slash.\n>     \techo \"$file\" | grep -F '//' && return 1\n>     \tdirs=$(echo \"$file\" | sed -r 's!/[^/]+$!!')\n\nGNUism already pointed out, I think.\n>\n>     \t# We touch \"./$file\" instead of \"$file\" because even an\n>     \t# escaped \"touch -- -\" means something different.\n>     \tif test \"$file\" != \"$dirs\"\n>     \tthen\n>     \t\tmkdir -p -- \"$dirs\" 2>/dev/null &&\n>     \t\ttouch -- \"./$file\" 2>/dev/null &&\n>     \t\treturn 0\n>     \telse\n>     \t\ttouch -- \"./$file\" 2>/dev/null &&\n>     \t\treturn 0\n>     \tfi\n>     \treturn 1\n>     }\n>\n> And then later on for the tests I do:\n>\n> \t# The existing test\n> \ttest_expect_success \"wildmatch:     match '$text' '$pattern'\" \"\n> \t\ttest-wildmatch wildmatch '$text' '$pattern'\n> \t\"\n>\n> \t# My new test\n> \tif create_test_file \"$text\"\n> \tthen\n> \t\ttest_expect_success \"wildmatch(ls): match '$pattern' '$text'\" \"\n> \t\t\ttest_when_finished \\\"\n> \t\t\t\trm -rf -- * &&\n> \t\t\t\tgit reset\n> \t\t\t\\\" &&\n> \t\t\tgit add -A &&\n> \t\t\t>expect.err &&\n> \t\t\tprintf '%s' '$text' >expect &&\n> \t\t\tgit --glob-pathspecs ls-files -z -- '$pattern' 2>actual.err | tr -d '\\0' >actual &&\n> \t\t\ttest_cmp expect.err actual.err &&\n> \t\t\ttest_cmp expect actual\n> \t\t\"\n> \telse\n> \t\ttest_expect_failure \"wildmatch(ls): match skip '$pattern' '$text'\" 'false'\n> \tfi\n>\n> This still needs to be cleaned up a bit to be parameterized (i.e. the\n> --glob-pathspecs argument, whether it should error etc.).\n>\n> It works for me on Linux, but I'm wondering if others see any issues\n> with the approach, does simply trying to create bizarro filenames on\n> some OSs cause issues? I don't think so, but let's make sure.\n\nIssues meaning that the test wants to see how a pathname with ^I in\nit works but create_test_file step would fail?  Your above construct\ncovers that with the if/then/else test_expect_failure/fi just fine,\nI think.\n"}]}