Git Distributed Software Revision Control — Thread Index

• Date Index

• Re: [PATCH v3 03/11] i18n: turn "options are incompatible" into "cannot be used together", (continued)
  • Re: [PATCH v3 03/11] i18n: turn "options are incompatible" into "cannot be used together", Jean-Noël AVILA
    • Re: [PATCH v3 03/11] i18n: turn "options are incompatible" into "cannot be used together", Junio C Hamano
  • [PATCH v3 05/11] i18n: tag.c factorize i18n strings, Jean-Noël Avila via GitGitGadget
    • Re: [PATCH v3 05/11] i18n: tag.c factorize i18n strings, René Scharfe
  • [PATCH v3 08/11] i18n: refactor "unrecognized %(foo) argument" strings, Jean-Noël Avila via GitGitGadget
  • [PATCH v3 07/11] i18n: factorize "no directory given for --foo", Jean-Noël Avila via GitGitGadget
    • Re: [PATCH v3 07/11] i18n: factorize "no directory given for --foo", Junio C Hamano
  • [PATCH v3 11/11] i18n: turn even more messages into "cannot be used together" ones, Jean-Noël Avila via GitGitGadget
    • Re: [PATCH v3 11/11] i18n: turn even more messages into "cannot be used together" ones, Junio C Hamano
      • Re: [PATCH v3 11/11] i18n: turn even more messages into "cannot be used together" ones, Jean-Noël AVILA
        • Re: [PATCH v3 11/11] i18n: turn even more messages into "cannot be used together" ones, Junio C Hamano
  • [PATCH v3 10/11] i18n: ref-filter: factorize "%(foo) atom used without %(bar) atom", Jean-Noël Avila via GitGitGadget
  • [PATCH v3 09/11] i18n: factorize "--foo outside a repository", Jean-Noël Avila via GitGitGadget
  • [PATCH v3 06/11] i18n: factorize "--foo requires --bar" and the like, Jean-Noël Avila via GitGitGadget
  • [PATCH v4 00/11] Factorization of messages with similar meaning, Jean-Noël Avila via GitGitGadget
    • [PATCH v4 01/11] i18n: refactor "foo and bar are mutually exclusive", Jean-Noël Avila via GitGitGadget
    • [PATCH v4 03/11] i18n: turn "options are incompatible" into "cannot be used together", Jean-Noël Avila via GitGitGadget
    • [PATCH v4 05/11] i18n: tag.c factorize i18n strings, Jean-Noël Avila via GitGitGadget
      • Re: [PATCH v4 05/11] i18n: tag.c factorize i18n strings, René Scharfe
        • Re: [PATCH v4 05/11] i18n: tag.c factorize i18n strings, Jean-Noël AVILA
    • [PATCH v4 08/11] i18n: refactor "unrecognized %(foo) argument" strings, Jean-Noël Avila via GitGitGadget
    • [PATCH v4 02/11] i18n: refactor "%s, %s and %s are mutually exclusive", Jean-Noël Avila via GitGitGadget
      • Re: [PATCH v4 02/11] i18n: refactor "%s, %s and %s are mutually exclusive", Johannes Sixt
    • [PATCH v4 04/11] i18n: standardize "cannot open" and "cannot read", Jean-Noël Avila via GitGitGadget
    • [PATCH v4 07/11] i18n: factorize "no directory given for --foo", Jean-Noël Avila via GitGitGadget
    • [PATCH v4 06/11] i18n: factorize "--foo requires --bar" and the like, Jean-Noël Avila via GitGitGadget
    • [PATCH v4 09/11] i18n: factorize "--foo outside a repository", Jean-Noël Avila via GitGitGadget
    • [PATCH v4 10/11] i18n: ref-filter: factorize "%(foo) atom used without %(bar) atom", Jean-Noël Avila via GitGitGadget
    • [PATCH v4 11/11] i18n: turn even more messages into "cannot be used together" ones, Jean-Noël Avila via GitGitGadget
    • [PATCH v5 00/11] Factorization of messages with similar meaning, Jean-Noël Avila via GitGitGadget
      • [PATCH v5 01/11] i18n: refactor "foo and bar are mutually exclusive", Jean-Noël Avila via GitGitGadget
      • [PATCH v5 02/11] i18n: refactor "%s, %s and %s are mutually exclusive", Jean-Noël Avila via GitGitGadget
      • [PATCH v5 04/11] i18n: standardize "cannot open" and "cannot read", Jean-Noël Avila via GitGitGadget
      • [PATCH v5 03/11] i18n: turn "options are incompatible" into "cannot be used together", Jean-Noël Avila via GitGitGadget
      • [PATCH v5 05/11] i18n: tag.c factorize i18n strings, Jean-Noël Avila via GitGitGadget
      • [PATCH v5 07/11] i18n: factorize "no directory given for --foo", Jean-Noël Avila via GitGitGadget
      • [PATCH v5 06/11] i18n: factorize "--foo requires --bar" and the like, Jean-Noël Avila via GitGitGadget
      • [PATCH v5 08/11] i18n: refactor "unrecognized %(foo) argument" strings, Jean-Noël Avila via GitGitGadget
      • [PATCH v5 11/11] i18n: turn even more messages into "cannot be used together" ones, Jean-Noël Avila via GitGitGadget
      • [PATCH v5 09/11] i18n: factorize "--foo outside a repository", Jean-Noël Avila via GitGitGadget
      • [PATCH v5 10/11] i18n: ref-filter: factorize "%(foo) atom used without %(bar) atom", Jean-Noël Avila via GitGitGadget
      • Re: [PATCH v5 00/11] Factorization of messages with similar meaning, Johannes Sixt
        • Re: [PATCH v5 00/11] Factorization of messages with similar meaning, Junio C Hamano
• [PATCH 0/2] worktree: fix incorrectly-ordered messages on Windows, Eric Sunshine
  • [PATCH 1/2] worktree: send "chatty" messages to stderr, Eric Sunshine
    • Re: [PATCH 1/2] worktree: send "chatty" messages to stderr, Ævar Arnfjörð Bjarmason
      • Re: [PATCH 1/2] worktree: send "chatty" messages to stderr, Eric Sunshine
  • [PATCH 2/2] git-worktree.txt: add missing `-v` to synopsis for `worktree list`, Eric Sunshine
    • Re: [PATCH 2/2] git-worktree.txt: add missing `-v` to synopsis for `worktree list`, Ævar Arnfjörð Bjarmason
      • Re: [PATCH 2/2] git-worktree.txt: add missing `-v` to synopsis for `worktree list`, Eric Sunshine
        • Re: [PATCH 2/2] git-worktree.txt: add missing `-v` to synopsis for `worktree list`, Ævar Arnfjörð Bjarmason
          • Re: [PATCH 2/2] git-worktree.txt: add missing `-v` to synopsis for `worktree list`, Jeff King
        • Re: [PATCH 2/2] git-worktree.txt: add missing `-v` to synopsis for `worktree list`, Junio C Hamano
          • Re: [PATCH 2/2] git-worktree.txt: add missing `-v` to synopsis for `worktree list`, Eric Sunshine
            • Re: [PATCH 2/2] git-worktree.txt: add missing `-v` to synopsis for `worktree list`, Ævar Arnfjörð Bjarmason
              • Re: [PATCH 2/2] git-worktree.txt: add missing `-v` to synopsis for `worktree list`, Junio C Hamano
    • Re: [PATCH 2/2] git-worktree.txt: add missing `-v` to synopsis for `worktree list`, Rafael Silva
• Confusing (maybe wrong?) conflict output with ort, Alex Xu (Hello71)
  • Re: Confusing (maybe wrong?) conflict output with ort, Elijah Newren
    • Re: Confusing (maybe wrong?) conflict output with ort, Alex Xu (Hello71)
• [RFC PATCH 0/1] making --set-upstream have default arguments, Abhradeep Chakraborty
  • [RFC PATCH 1/1] push: make '-u' have default arguments, Abhradeep Chakraborty
    • Re: [RFC PATCH 1/1] push: make '-u' have default arguments, Junio C Hamano
      • Re: [RFC PATCH 1/1] push: make '-u' have default arguments, Abhradeep Chakraborty
        • Re: [RFC PATCH 1/1] push: make '-u' have default arguments, Junio C Hamano
          • Re: [RFC PATCH 1/1] push: make '-u' have default arguments, Abhradeep Chakraborty
  • Re: [RFC PATCH 0/1] making --set-upstream have default arguments, Philip Oakley
    • Re: [RFC PATCH 0/1] making --set-upstream have default arguments, Abhradeep Chakraborty
      • Re: [RFC PATCH 0/1] making --set-upstream have default arguments, Philip Oakley
    • Re: [RFC PATCH 0/1] making --set-upstream have default arguments, Abhradeep Chakraborty
  • [PATCH v2 0/1] making --set-upstream have default arguments, Abhradeep Chakraborty
    • [PATCH v2 1/1] push: make '-u' have default arguments, Abhradeep Chakraborty
      • Re: [PATCH v2 1/1] push: make '-u' have default arguments, Eric Sunshine
        • Re: [PATCH v2 1/1] push: make '-u' have default argument, Abhradeep Chakraborty
    • [PATCH v3 0/1] making --set-upstream have default arguments, Abhradeep Chakraborty
      • [PATCH v3 1/1] push: make '-u' have default arguments, Abhradeep Chakraborty
      • [PATCH v4 0/1] making --set-upstream have default arguments, Abhradeep Chakraborty
        • [PATCH v4 1/1] push: make 'set-upstream' have dafault arguments, Abhradeep Chakraborty
          • Re: [PATCH v4 1/1] push: make 'set-upstream' have dafault arguments, Junio C Hamano
            • Re: [PATCH v4 1/1] push: make 'set-upstream' have dafault arguments, Abhradeep Chakraborty
              • Re: [PATCH v4 1/1] push: make 'set-upstream' have dafault arguments, Junio C Hamano
• [RFC PATCH 0/3] editor: teach it to protect itself from rogue editors, Carlo Marcelo Arenas Belón
  • [RFC PATCH 1/3] terminal: teach save_term to fail when not foreground, Carlo Marcelo Arenas Belón
  • [RFC PATCH 2/3] editor: allow for saving/restoring terminal state, Carlo Marcelo Arenas Belón
    • Re: [RFC PATCH 2/3] editor: allow for saving/restoring terminal state, Junio C Hamano
  • [RFC PATCH 3/3] fixup! editor: allow for saving/restoring terminal state, Carlo Marcelo Arenas Belón
• Potential bug with octopus merges and symlinks, Michael McClimon
  • Re: Potential bug with octopus merges and symlinks, Elijah Newren
  • Re: Potential bug with octopus merges and symlinks, Martin von Zweigbergk
  • Re: Potential bug with octopus merges and symlinks, Junio C Hamano
• [PATCH] http-backend: give a hint that web browser access is not supported, Jan Engelhardt
  • Re: [PATCH] http-backend: give a hint that web browser access is not supported, Junio C Hamano
    • RFE: Split diff.noprefix for git-diff and git-format-patch (was: http-backend: give a hint that web browser access is not supported), Jan Engelhardt
      • Re: RFE: Split diff.noprefix for git-diff and git-format-patch, Junio C Hamano
    • [PATCH] http-backend: give a hint that web browser access is not supported, Jan Engelhardt
      • Re: [PATCH] http-backend: give a hint that web browser access is not supported, Junio C Hamano
        • Re: [PATCH] http-backend: give a hint that web browser access is not supported, Jan Engelhardt
          • Re: [PATCH] http-backend: give a hint that web browser access is not supported, Junio C Hamano
            • Re: [PATCH] http-backend: give a hint that web browser access is not supported, Jan Engelhardt
              • Re: [PATCH] http-backend: give a hint that web browser access is not supported, Junio C Hamano
                • Re: [PATCH] http-backend: give a hint that web browser access is not supported, Junio C Hamano
• [PATCH 1/2] http-backend: CGI error messages need to be output on stdout, Jan Engelhardt
  • [PATCH 2/2] http-backend: give a hint that web browser access is not supported, Jan Engelhardt
  • Re: [PATCH 1/2] http-backend: CGI error messages need to be output on stdout, Junio C Hamano
• [PATCH v7 0/8] protect branches checked out in all worktrees, Anders Kaseorg
  • [PATCH v7 1/8] fetch: lowercase error messages, Anders Kaseorg
  • [PATCH v7 3/8] branch: lowercase error messages, Anders Kaseorg
  • [PATCH v7 4/8] worktree: simplify find_shared_symref() memory ownership model, Anders Kaseorg
    • Re: [PATCH v7 4/8] worktree: simplify find_shared_symref() memory ownership model, Eric Sunshine
      • Re: [PATCH v7 4/8] worktree: simplify find_shared_symref() memory ownership model, Anders Kaseorg
        • Re: [PATCH v7 4/8] worktree: simplify find_shared_symref() memory ownership model, Eric Sunshine
          • Re: [PATCH v7 4/8] worktree: simplify find_shared_symref() memory ownership model, Eric Sunshine
          • Re: [PATCH v7 4/8] worktree: simplify find_shared_symref() memory ownership model, Anders Kaseorg
            • Re: [PATCH v7 4/8] worktree: simplify find_shared_symref() memory ownership model, Eric Sunshine
  • [PATCH v7 2/8] receive-pack: lowercase error messages, Anders Kaseorg
  • [PATCH v7 5/8] fetch: protect branches checked out in all worktrees, Anders Kaseorg
    • Re: [PATCH v7 5/8] fetch: protect branches checked out in all worktrees, Eric Sunshine
      • Re: [PATCH v7 5/8] fetch: protect branches checked out in all worktrees, Anders Kaseorg
  • [PATCH v7 6/8] receive-pack: clean dead code from update_worktree(), Anders Kaseorg
  • [PATCH v7 7/8] receive-pack: protect current branch for bare repository worktree, Anders Kaseorg
  • [PATCH v7 8/8] branch: protect branches checked out in all worktrees, Anders Kaseorg
    • Re: [PATCH v7 8/8] branch: protect branches checked out in all worktrees, Jiang Xin
      • Re: [PATCH v7 8/8] branch: protect branches checked out in all worktrees, Jiang Xin
        • Re: [PATCH v7 8/8] branch: protect branches checked out in all worktrees, Junio C Hamano
• 2.34 regression (and workaround): deleting untracked files both outside *and inside* desired sparsity cone, Elijah Newren
  • Re: 2.34 regression (and workaround): deleting untracked files both outside *and inside* desired sparsity cone, Derrick Stolee
    • Re: 2.34 regression (and workaround): deleting untracked files both outside *and inside* desired sparsity cone, Elijah Newren
      • Re: 2.34 regression (and workaround): deleting untracked files both outside *and inside* desired sparsity cone, Derrick Stolee
• Merge conflict when lines next to each other are changed, Loic Fouray
  • RE: Merge conflict when lines next to each other are changed, rsbecker
    • Re: Merge conflict when lines next to each other are changed, Loic Fouray
      • RE: Merge conflict when lines next to each other are changed, rsbecker
    • Re: Merge conflict when lines next to each other are changed, Loic Fouray
      • RE: Merge conflict when lines next to each other are changed, rsbecker
  • Re: Merge conflict when lines next to each other are changed, Jean-Noël Avila
    • Re: Merge conflict when lines next to each other are changed, Loic Fouray
• [PATCH] CodingGuidelines: document which output goes to stdout vs. stderr, Eric Sunshine
  • Re: [PATCH] CodingGuidelines: document which output goes to stdout vs. stderr, Fabian Stelzer
    • Re: [PATCH] CodingGuidelines: document which output goes to stdout vs. stderr, Eric Sunshine
      • Re: [PATCH] CodingGuidelines: document which output goes to stdout vs. stderr, Fabian Stelzer
      • Re: [PATCH] CodingGuidelines: document which output goes to stdout vs. stderr, Junio C Hamano
        • Re: [PATCH] CodingGuidelines: document which output goes to stdout vs. stderr, Eric Sunshine
  • Re: [PATCH] CodingGuidelines: document which output goes to stdout vs. stderr, Jeff King
    • Re: [PATCH] CodingGuidelines: document which output goes to stdout vs. stderr, Eric Sunshine
  • Re: [PATCH] CodingGuidelines: document which output goes to stdout vs. stderr, Philip Oakley
    • Re: [PATCH] CodingGuidelines: document which output goes to stdout vs. stderr, Eric Sunshine
  • [PATCH v2] CodingGuidelines: document which output goes to stdout vs. stderr, Eric Sunshine
    • Re: [PATCH v2] CodingGuidelines: document which output goes to stdout vs. stderr, Jeff King
• [PATCH] subtree: fix argument handling in check_parents, James Limbouris via GitGitGadget
  • Re: [PATCH] subtree: fix argument handling in check_parents, Junio C Hamano
  • [PATCH v2] subtree: fix argument handling in check_parents, James Limbouris via GitGitGadget
    • [PATCH v3] subtree: fix argument handling in check_parents, James Limbouris via GitGitGadget
      • [PATCH v4] subtree: fix argument handling in check_parents, James Limbouris via GitGitGadget
        • Re: [PATCH v4] subtree: fix argument handling in check_parents, Johannes Schindelin
          • Re: [PATCH v4] subtree: fix argument handling in check_parents, Junio C Hamano
  • Re: [PATCH] subtree: fix argument handling in check_parents, Johannes Schindelin
    • Re: [PATCH] subtree: fix argument handling in check_parents, Junio C Hamano
    • Re: [PATCH] subtree: fix argument handling in check_parents, Johannes Schindelin
• [PATCH v2 0/3] Fix LLP64 `(size_t)1` compatibility VS C4334 warnings, Philip Oakley
  • [PATCH v2 1/3] repack.c: LLP64 compatibility, upcast unity for left shift, Philip Oakley
  • [PATCH v2 2/3] diffcore-delta.c: LLP64 compatibility, upcast unity for left shift, Philip Oakley
  • [PATCH v2 3/3] object-file.c: LLP64 compatibility, upcast unity for left shift, Philip Oakley
  • Re: [PATCH v2 0/3] Fix LLP64 `(size_t)1` compatibility VS C4334 warnings, Junio C Hamano
    • Re: [PATCH v2 0/3] Fix LLP64 `(size_t)1` compatibility VS C4334 warnings, Derrick Stolee
• [PATCH 00/12] reflog + gc: refactor, progress output, reftable-readyness, Ævar Arnfjörð Bjarmason
  • [PATCH 01/12] reflog delete: narrow scope of "cmd" passed to count_reflog_ent(), Ævar Arnfjörð Bjarmason
  • [PATCH 02/12] reflog expire: narrow scope of "cb" in cmd_reflog_expire(), Ævar Arnfjörð Bjarmason
  • [PATCH 03/12] reflog: change one->many worktree->refnames to use a string_list, Ævar Arnfjörð Bjarmason
  • [PATCH 04/12] reflog expire: don't do negative comparison on enum values, Ævar Arnfjörð Bjarmason
  • [PATCH 05/12] reflog expire: refactor & use "tip_commit" only for UE_NORMAL, Ævar Arnfjörð Bjarmason
  • [PATCH 06/12] reflog expire: don't use lookup_commit_reference_gently(), Ævar Arnfjörð Bjarmason
  • [PATCH 07/12] reflog: reduce scope of "struct rev_info", Ævar Arnfjörð Bjarmason
  • [PATCH 09/12] reflog + refs-backend: move "verbose" out of the backend, Ævar Arnfjörð Bjarmason
  • [PATCH 11/12] gc + reflog: emit progress output from "reflog expire --all", Ævar Arnfjörð Bjarmason
  • [PATCH 10/12] reflog expire: add progress output on --stale-fix, Ævar Arnfjörð Bjarmason
  • [PATCH 08/12] refs files-backend: assume cb->newlog if !EXPIRE_REFLOGS_DRY_RUN, Ævar Arnfjörð Bjarmason
  • [PATCH 12/12] gc + reflog: don't stall before initial "git gc" progress output, Ævar Arnfjörð Bjarmason
  • [PATCH v2 0/9] reftable prep: have builtin/reflog.c handle "--verbose", Ævar Arnfjörð Bjarmason
    • [PATCH v2 1/9] reflog delete: narrow scope of "cmd" passed to count_reflog_ent(), Ævar Arnfjörð Bjarmason
    • [PATCH v2 2/9] reflog expire: narrow scope of "cb" in cmd_reflog_expire(), Ævar Arnfjörð Bjarmason
    • [PATCH v2 3/9] reflog: change one->many worktree->refnames to use a string_list, Ævar Arnfjörð Bjarmason
    • [PATCH v2 4/9] reflog expire: don't do negative comparison on enum values, Ævar Arnfjörð Bjarmason
    • [PATCH v2 5/9] reflog expire: refactor & use "tip_commit" only for UE_NORMAL, Ævar Arnfjörð Bjarmason
    • [PATCH v2 6/9] reflog expire: don't use lookup_commit_reference_gently(), Ævar Arnfjörð Bjarmason
    • [PATCH v2 7/9] reflog: reduce scope of "struct rev_info", Ævar Arnfjörð Bjarmason
    • [PATCH v2 8/9] refs files-backend: assume cb->newlog if !EXPIRE_REFLOGS_DRY_RUN, Ævar Arnfjörð Bjarmason
    • [PATCH v2 9/9] reflog + refs-backend: move "verbose" out of the backend, Ævar Arnfjörð Bjarmason
    • Re: [PATCH v2 0/9] reftable prep: have builtin/reflog.c handle "--verbose", Junio C Hamano
      • Re: [PATCH v2 0/9] reftable prep: have builtin/reflog.c handle "--verbose", Ævar Arnfjörð Bjarmason
    • Re: [PATCH v2 0/9] reftable prep: have builtin/reflog.c handle "--verbose", Han-Wen Nienhuys
      • Re: [PATCH v2 0/9] reftable prep: have builtin/reflog.c handle "--verbose", Ævar Arnfjörð Bjarmason
    • [PATCH v3 0/9] reftable prep: have builtin/reflog.c handle "--verbose", Ævar Arnfjörð Bjarmason
      • [PATCH v3 1/9] reflog delete: narrow scope of "cmd" passed to count_reflog_ent(), Ævar Arnfjörð Bjarmason
      • [PATCH v3 2/9] reflog expire: narrow scope of "cb" in cmd_reflog_expire(), Ævar Arnfjörð Bjarmason
      • [PATCH v3 3/9] reflog: change one->many worktree->refnames to use a string_list, Ævar Arnfjörð Bjarmason
      • [PATCH v3 4/9] reflog expire: use "switch" over enum values, Ævar Arnfjörð Bjarmason
      • [PATCH v3 7/9] reflog: reduce scope of "struct rev_info", Ævar Arnfjörð Bjarmason
      • [PATCH v3 6/9] reflog expire: don't use lookup_commit_reference_gently(), Ævar Arnfjörð Bjarmason
      • [PATCH v3 5/9] reflog expire: refactor & use "tip_commit" only for UE_NORMAL, Ævar Arnfjörð Bjarmason
      • [PATCH v3 8/9] refs files-backend: assume cb->newlog if !EXPIRE_REFLOGS_DRY_RUN, Ævar Arnfjörð Bjarmason
      • [PATCH v3 9/9] reflog + refs-backend: move "verbose" out of the backend, Ævar Arnfjörð Bjarmason
• `git diff` after `git checkout from-branch -- files` reports nothing, Noel Yap
  • Re: `git diff` after `git checkout from-branch -- files` reports nothing, Bryan Turner
    • Re: `git diff` after `git checkout from-branch -- files` reports nothing, Noel Yap
• [PATCH v3 0/3] vimdiff: new implementation with layout support, Fernando Ramos
  • [PATCH v3 1/3] vimdiff: new implementation with layout support, Fernando Ramos
  • [PATCH v3 2/3] vimdiff: add tool documentation, Fernando Ramos
    • Re: [PATCH v3 2/3] vimdiff: add tool documentation, Ævar Arnfjörð Bjarmason
      • Re: [PATCH v3 2/3] vimdiff: add tool documentation, Fernando Ramos
  • [PATCH v3 3/3] vimdiff: integrate layout tests in the unit tests framework ('t' folder), Fernando Ramos
    • Re: [PATCH v3 3/3] vimdiff: integrate layout tests in the unit tests framework ('t' folder), Ævar Arnfjörð Bjarmason
  • Re: [PATCH v3 0/3] vimdiff: new implementation with layout support, Eric Sunshine
    • Re: [PATCH v3 0/3] vimdiff: new implementation with layout support, Fernando Ramos
• [PATCH 0/2] Use the built-in implementation of the interactive add command by default, Johannes Schindelin via GitGitGadget
  • [PATCH 1/2] t2016: require the PERL prereq only when necessary, Johannes Schindelin via GitGitGadget
    • Re: [PATCH 1/2] t2016: require the PERL prereq only when necessary, Junio C Hamano
      • Re: [PATCH 1/2] t2016: require the PERL prereq only when necessary, Johannes Schindelin
  • [PATCH 2/2] add -i: default to the built-in implementation, Johannes Schindelin via GitGitGadget
    • Re: [PATCH 2/2] add -i: default to the built-in implementation, Phillip Wood
      • Re: [PATCH 2/2] add -i: default to the built-in implementation, Johannes Schindelin
        • Re: [PATCH 2/2] add -i: default to the built-in implementation, Junio C Hamano
          • Re: [PATCH 2/2] add -i: default to the built-in implementation, Ramsay Jones
          • Re: [PATCH 2/2] add -i: default to the built-in implementation, Johannes Schindelin
    • Re: [PATCH 2/2] add -i: default to the built-in implementation, Ævar Arnfjörð Bjarmason
      • Re: [PATCH 2/2] add -i: default to the built-in implementation, Junio C Hamano
    • Re: [PATCH 2/2] add -i: default to the built-in implementation, Junio C Hamano
      • Re: [PATCH 2/2] add -i: default to the built-in implementation, Johannes Schindelin
    • [PATCH] fixup! add -i: default to the built-in implementation, Junio C Hamano
      • Re: [PATCH] fixup! add -i: default to the built-in implementation, Johannes Schindelin
  • Re: [PATCH 0/2] Use the built-in implementation of the interactive add command by default, Jeff King
  • Re: [PATCH 0/2] Use the built-in implementation of the interactive add command by default, Junio C Hamano
  • Re: [PATCH 0/2] Use the built-in implementation of the interactive add command by default, Ævar Arnfjörð Bjarmason
  • Re: [PATCH 0/2] Use the built-in implementation of the interactive add command by default, Carlo Arenas
    • Re: [PATCH 0/2] Use the built-in implementation of the interactive add command by default, Johannes Schindelin
  • Re: [PATCH 0/2] Use the built-in implementation of the interactive add command by default, Philippe Blain
    • Re: [PATCH 0/2] Use the built-in implementation of the interactive add command by default, Johannes Schindelin
• Will -fsyntax-only hide issues with -pedantic? I think not..., Ævar Arnfjörð Bjarmason
  • Re: Will -fsyntax-only hide issues with -pedantic? I think not..., Jeff King
• [RFC PATCH] vreportf: ensure sensible ordering of normal and error output, Eric Sunshine
  • Re: [RFC PATCH] vreportf: ensure sensible ordering of normal and error output, Junio C Hamano
    • Re: [RFC PATCH] vreportf: ensure sensible ordering of normal and error output, Jeff King
      • Re: [RFC PATCH] vreportf: ensure sensible ordering of normal and error output, Jeff King
        • Re: [RFC PATCH] vreportf: ensure sensible ordering of normal and error output, Ævar Arnfjörð Bjarmason
          • Re: [RFC PATCH] vreportf: ensure sensible ordering of normal and error output, Jeff King
      • Re: [RFC PATCH] vreportf: ensure sensible ordering of normal and error output, Eric Sunshine
  • Re: [RFC PATCH] vreportf: ensure sensible ordering of normal and error output, Jeff King
    • Re: [RFC PATCH] vreportf: ensure sensible ordering of normal and error output, Eric Sunshine
      • Re: [RFC PATCH] vreportf: ensure sensible ordering of normal and error output, Eric Sunshine
        • "breaking" command output message parsing (was: [RFC PATCH] vreportf: ensure sensible ordering of normal and error output), Ævar Arnfjörð Bjarmason
          • Re: "breaking" command output message parsing (was: [RFC PATCH] vreportf: ensure sensible ordering of normal and error output), Eric Sunshine
      • Re: [RFC PATCH] vreportf: ensure sensible ordering of normal and error output, Jeff King
        • Re: [RFC PATCH] vreportf: ensure sensible ordering of normal and error output, Eric Sunshine
          • Re: [RFC PATCH] vreportf: ensure sensible ordering of normal and error output, Eric Sunshine
        • Re: [RFC PATCH] vreportf: ensure sensible ordering of normal and error output, Ævar Arnfjörð Bjarmason
          • Re: [RFC PATCH] vreportf: ensure sensible ordering of normal and error output, Junio C Hamano
• [PATCH] sequencer: avoid adding exec commands for non-commit creating commands, Elijah Newren via GitGitGadget
  • Re: [PATCH] sequencer: avoid adding exec commands for non-commit creating commands, Taylor Blau
  • Re: [BUG REPORT] `git rebase --exec` shouldn't run the exec command when there is nothing to rebase, Ævar Arnfjörð Bjarmason
    • Re: [BUG REPORT] `git rebase --exec` shouldn't run the exec command when there is nothing to rebase, Phillip Wood
  • Re: [PATCH] sequencer: avoid adding exec commands for non-commit creating commands, Phillip Wood
  • Re: [PATCH] sequencer: avoid adding exec commands for non-commit creating commands, Johannes Schindelin
• What's cooking in git.git (Nov 2021, #07; Mon, 29), Junio C Hamano
  • jk/loosen-urlmatch, was What's cooking in git.git (Nov 2021, #07; Mon, 29), Jeff King
    • Re: jk/loosen-urlmatch, was What's cooking in git.git (Nov 2021, #07; Mon, 29), brian m. carlson
  • ab/run-command + em/missing-pager (was: What's cooking in git.git (Nov 2021, #07; Mon, 29)), Ævar Arnfjörð Bjarmason
    • Re: ab/run-command + em/missing-pager (was: What's cooking in git.git (Nov 2021, #07; Mon, 29)), Jeff King
    • Re: ab/run-command + em/missing-pager (was: What's cooking in git.git (Nov 2021, #07; Mon, 29)), Eric Sunshine
  • ab/ci-updates (was: What's cooking in git.git (Nov 2021, #07; Mon, 29)), Ævar Arnfjörð Bjarmason
  • ab/config-based-hooks-2 (was: What's cooking in git.git (Nov 2021, #07; Mon, 29)), Ævar Arnfjörð Bjarmason
  • fs/test-prereq (was: What's cooking in git.git (Nov 2021, #07; Mon, 29)), Ævar Arnfjörð Bjarmason
    • Re: fs/test-prereq (was: What's cooking in git.git (Nov 2021, #07; Mon, 29)), Fabian Stelzer
  • jc/c99-var-decl-in-for-loop (was: What's cooking in git.git (Nov 2021, #07; Mon, 29)), Ævar Arnfjörð Bjarmason
  • ns/tmp-objdir and ns/remerge-diff, Elijah Newren
    • Re: ns/tmp-objdir and ns/remerge-diff, Junio C Hamano
      • Re: ns/tmp-objdir and ns/remerge-diff, Neeraj Singh
        • Re: ns/tmp-objdir and ns/remerge-diff, Elijah Newren
  • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Elijah Newren
    • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Victoria Dye
  • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Elijah Newren
    • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Aleen 徐沛文
      • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Elijah Newren
        • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Ævar Arnfjörð Bjarmason
          • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Elijah Newren
            • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Ævar Arnfjörð Bjarmason
              • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Aleen 徐沛文
                • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Junio C Hamano
                  • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Aleen 徐沛文
                    • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Aleen 徐沛文
                    • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Junio C Hamano
                      • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Aleen 徐沛文
                        • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Junio C Hamano
                          • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Aleen 徐沛文
                  • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Elijah Newren
                    • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Junio C Hamano
  • en/zdiff3 (was: Re: What's cooking in git.git (Nov 2021, #07; Mon, 29)), Elijah Newren
    • Re: en/zdiff3, Junio C Hamano
  • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Fabian Stelzer
  • Re: What's cooking in git.git (Nov 2021, #07; Mon, 29), Junio C Hamano
  • [PATCH 0/3] unused-parameter cleanups on top of pw/xdiff-classify-record-in-histogram, Jeff King
    • [PATCH 1/3] xdiff: drop CMP_ENV macro from xhistogram, Jeff King
    • [PATCH 2/3] xdiff: drop xpparam_t parameter from histogram cmp_recs(), Jeff King
    • [PATCH 3/3] xdiff: drop unused flags parameter from recs_match, Jeff King
    • Re: [PATCH 0/3] unused-parameter cleanups on top of pw/xdiff-classify-record-in-histogram, Phillip Wood
• patch: change “Everything up-to-date” to “Already up to date.” (No-op messages for git-push and git-pull), Anselm Schüler
  • Re: patch: change “Everything up-to-date” to “Already up to date.” (No-op messages for git-push and git-pull), Eric Sunshine
    • Re: patch: change “Everything up-to-date” to “Already up to date.” (No-op messages for git-push and git-pull), Ævar Arnfjörð Bjarmason
    • Re: patch: change “Everything up-to-date��� to “Already up to date.” (No-op messages for git-push and git-pull), Johannes Schindelin
• [PATCH 00/17] cruft packs, Taylor Blau
  • [PATCH 01/17] Documentation/technical: add cruft-packs.txt, Taylor Blau
    • Re: [PATCH 01/17] Documentation/technical: add cruft-packs.txt, Derrick Stolee
      • Re: [PATCH 01/17] Documentation/technical: add cruft-packs.txt, Taylor Blau
    • Re: [PATCH 01/17] Documentation/technical: add cruft-packs.txt, Elijah Newren
      • Re: [PATCH 01/17] Documentation/technical: add cruft-packs.txt, Taylor Blau
  • [PATCH 02/17] pack-mtimes: support reading .mtimes files, Taylor Blau
    • Re: [PATCH 02/17] pack-mtimes: support reading .mtimes files, Derrick Stolee
      • Re: [PATCH 02/17] pack-mtimes: support reading .mtimes files, brian m. carlson
      • Re: [PATCH 02/17] pack-mtimes: support reading .mtimes files, Taylor Blau
        • Re: [PATCH 02/17] pack-mtimes: support reading .mtimes files, Taylor Blau
  • [PATCH 03/17] pack-write: pass 'struct packing_data' to 'stage_tmp_packfiles', Taylor Blau
  • [PATCH 05/17] pack-mtimes: support writing pack .mtimes files, Taylor Blau
    • Re: [PATCH 05/17] pack-mtimes: support writing pack .mtimes files, Derrick Stolee
      • Re: [PATCH 05/17] pack-mtimes: support writing pack .mtimes files, Taylor Blau
  • [PATCH 04/17] chunk-format.h: extract oid_version(), Taylor Blau
    • Re: [PATCH 04/17] chunk-format.h: extract oid_version(), Derrick Stolee
      • Re: [PATCH 04/17] chunk-format.h: extract oid_version(), Taylor Blau
        • Re: [PATCH 04/17] chunk-format.h: extract oid_version(), Derrick Stolee
  • [PATCH 09/17] reachable: add options to add_unseen_recent_objects_to_traversal, Taylor Blau
  • [PATCH 06/17] t/helper: add 'pack-mtimes' test-tool, Taylor Blau
    • Re: [PATCH 06/17] t/helper: add 'pack-mtimes' test-tool, Derrick Stolee
      • Re: [PATCH 06/17] t/helper: add 'pack-mtimes' test-tool, Taylor Blau
  • [PATCH 13/17] builtin/repack.c: allow configuring cruft pack generation, Taylor Blau
  • [PATCH 11/17] builtin/pack-objects.c: --cruft with expiration, Taylor Blau
    • Re: [PATCH 11/17] builtin/pack-objects.c: --cruft with expiration, Derrick Stolee
      • Re: [PATCH 11/17] builtin/pack-objects.c: --cruft with expiration, Taylor Blau
  • [PATCH 10/17] reachable: report precise timestamps from objects in cruft packs, Taylor Blau
  • [PATCH 07/17] builtin/pack-objects.c: return from create_object_entry(), Taylor Blau
  • [PATCH 08/17] builtin/pack-objects.c: --cruft without expiration, Taylor Blau
    • Re: [PATCH 08/17] builtin/pack-objects.c: --cruft without expiration, Derrick Stolee
      • Re: [PATCH 08/17] builtin/pack-objects.c: --cruft without expiration, Taylor Blau
    • Re: [PATCH 08/17] builtin/pack-objects.c: --cruft without expiration, Derrick Stolee
      • Re: [PATCH 08/17] builtin/pack-objects.c: --cruft without expiration, Taylor Blau
  • [PATCH 12/17] builtin/repack.c: support generating a cruft pack, Taylor Blau
    • Re: [PATCH 12/17] builtin/repack.c: support generating a cruft pack, Junio C Hamano
      • Re: [PATCH 12/17] builtin/repack.c: support generating a cruft pack, Taylor Blau
    • Re: [PATCH 12/17] builtin/repack.c: support generating a cruft pack, Derrick Stolee
      • Re: [PATCH 12/17] builtin/repack.c: support generating a cruft pack, Taylor Blau
  • [PATCH 15/17] builtin/repack.c: add cruft packs to MIDX during geometric repack, Taylor Blau
  • [PATCH 16/17] builtin/gc.c: conditionally avoid pruning objects via loose, Taylor Blau
  • [PATCH 17/17] sha1-file.c: don't freshen cruft packs, Taylor Blau
  • [PATCH 14/17] builtin/repack.c: use named flags for existing_packs, Taylor Blau
  • Re: [PATCH 00/17] cruft packs, Junio C Hamano
    • Re: [PATCH 00/17] cruft packs, Taylor Blau
      • Re: [PATCH 00/17] cruft packs, Taylor Blau
  • [PATCH v2 00/17] cruft packs, Taylor Blau
    • [PATCH v2 01/17] Documentation/technical: add cruft-packs.txt, Taylor Blau
    • [PATCH v2 06/17] t/helper: add 'pack-mtimes' test-tool, Taylor Blau
    • [PATCH v2 02/17] pack-mtimes: support reading .mtimes files, Taylor Blau
      • Re: [PATCH v2 02/17] pack-mtimes: support reading .mtimes files, Derrick Stolee
        • Re: [PATCH v2 02/17] pack-mtimes: support reading .mtimes files, Taylor Blau
    • [PATCH v2 03/17] pack-write: pass 'struct packing_data' to 'stage_tmp_packfiles', Taylor Blau
    • [PATCH v2 05/17] pack-mtimes: support writing pack .mtimes files, Taylor Blau
    • [PATCH v2 04/17] chunk-format.h: extract oid_version(), Taylor Blau
    • [PATCH v2 07/17] builtin/pack-objects.c: return from create_object_entry(), Taylor Blau
    • [PATCH v2 11/17] builtin/pack-objects.c: --cruft with expiration, Taylor Blau
      • Re: [PATCH v2 11/17] builtin/pack-objects.c: --cruft with expiration, Junio C Hamano
        • Re: [PATCH v2 11/17] builtin/pack-objects.c: --cruft with expiration, Taylor Blau
          • Re: [PATCH v2 11/17] builtin/pack-objects.c: --cruft with expiration, Derrick Stolee
    • [PATCH v2 08/17] builtin/pack-objects.c: --cruft without expiration, Taylor Blau
    • [PATCH v2 09/17] reachable: add options to add_unseen_recent_objects_to_traversal, Taylor Blau
      • Re: [PATCH v2 09/17] reachable: add options to add_unseen_recent_objects_to_traversal, Derrick Stolee
        • Re: [PATCH v2 09/17] reachable: add options to add_unseen_recent_objects_to_traversal, Taylor Blau
    • [PATCH v2 10/17] reachable: report precise timestamps from objects in cruft packs, Taylor Blau
    • [PATCH v2 12/17] builtin/repack.c: support generating a cruft pack, Taylor Blau
    • [PATCH v2 14/17] builtin/repack.c: use named flags for existing_packs, Taylor Blau
    • [PATCH v2 13/17] builtin/repack.c: allow configuring cruft pack generation, Taylor Blau
    • [PATCH v2 16/17] builtin/gc.c: conditionally avoid pruning objects via loose, Taylor Blau
    • [PATCH v2 15/17] builtin/repack.c: add cruft packs to MIDX during geometric repack, Taylor Blau
    • [PATCH v2 17/17] sha1-file.c: don't freshen cruft packs, Taylor Blau
    • Re: [PATCH v2 00/17] cruft packs, Derrick Stolee
      • Re: [PATCH v2 00/17] cruft packs, Taylor Blau
  • [PATCH v3 00/17] cruft packs, Taylor Blau
    • [PATCH v3 04/17] chunk-format.h: extract oid_version(), Taylor Blau
      • Re: [PATCH v3 04/17] chunk-format.h: extract oid_version(), Ævar Arnfjörð Bjarmason
        • Re: [PATCH v3 04/17] chunk-format.h: extract oid_version(), Taylor Blau
          • Re: [PATCH v3 04/17] chunk-format.h: extract oid_version(), Junio C Hamano
    • [PATCH v3 05/17] pack-mtimes: support writing pack .mtimes files, Taylor Blau
      • Re: [PATCH v3 05/17] pack-mtimes: support writing pack .mtimes files, Ævar Arnfjörð Bjarmason
        • Re: [PATCH v3 05/17] pack-mtimes: support writing pack .mtimes files, Taylor Blau
          • Re: [PATCH v3 05/17] pack-mtimes: support writing pack .mtimes files, Ævar Arnfjörð Bjarmason
    • [PATCH v3 01/17] Documentation/technical: add cruft-packs.txt, Taylor Blau
      • Re: [PATCH v3 01/17] Documentation/technical: add cruft-packs.txt, Jonathan Nieder
        • Re: [PATCH v3 01/17] Documentation/technical: add cruft-packs.txt, Taylor Blau
          • Re: [PATCH v3 01/17] Documentation/technical: add cruft-packs.txt, Jonathan Nieder
            • Re: [PATCH v3 01/17] Documentation/technical: add cruft-packs.txt, Taylor Blau
              • Re: [PATCH v3 01/17] Documentation/technical: add cruft-packs.txt, Jonathan Nieder
                • Re: [PATCH v3 01/17] Documentation/technical: add cruft-packs.txt, Taylor Blau
                  • Re: [PATCH v3 01/17] Documentation/technical: add cruft-packs.txt, Taylor Blau
                    • Re: [PATCH v3 01/17] Documentation/technical: add cruft-packs.txt, Junio C Hamano
                      • Re: [PATCH v3 01/17] Documentation/technical: add cruft-packs.txt, Taylor Blau
                        • Re: [PATCH v3 01/17] Documentation/technical: add cruft-packs.txt, Junio C Hamano
                          • Re: [PATCH v3 01/17] Documentation/technical: add cruft-packs.txt, Taylor Blau
                            • Re: [PATCH v3 01/17] Documentation/technical: add cruft-packs.txt, Junio C Hamano
                              • Re: [PATCH v3 01/17] Documentation/technical: add cruft-packs.txt, Taylor Blau
    • [PATCH v3 02/17] pack-mtimes: support reading .mtimes files, Taylor Blau
    • [PATCH v3 03/17] pack-write: pass 'struct packing_data' to 'stage_tmp_packfiles', Taylor Blau
    • [PATCH v3 06/17] t/helper: add 'pack-mtimes' test-tool, Taylor Blau
    • [PATCH v3 09/17] reachable: add options to add_unseen_recent_objects_to_traversal, Taylor Blau
    • [PATCH v3 07/17] builtin/pack-objects.c: return from create_object_entry(), Taylor Blau
    • [PATCH v3 13/17] builtin/repack.c: allow configuring cruft pack generation, Taylor Blau
    • [PATCH v3 10/17] reachable: report precise timestamps from objects in cruft packs, Taylor Blau
    • [PATCH v3 17/17] sha1-file.c: don't freshen cruft packs, Taylor Blau
    • [PATCH v3 14/17] builtin/repack.c: use named flags for existing_packs, Taylor Blau
    • [PATCH v3 16/17] builtin/gc.c: conditionally avoid pruning objects via loose, Taylor Blau
    • [PATCH v3 11/17] builtin/pack-objects.c: --cruft with expiration, Taylor Blau
    • [PATCH v3 08/17] builtin/pack-objects.c: --cruft without expiration, Taylor Blau
    • [PATCH v3 12/17] builtin/repack.c: support generating a cruft pack, Taylor Blau
    • [PATCH v3 15/17] builtin/repack.c: add cruft packs to MIDX during geometric repack, Taylor Blau
    • Re: [PATCH v3 00/17] cruft packs, Derrick Stolee
  • [PATCH v4 00/17] cruft packs, Taylor Blau
    • [PATCH v4 15/17] builtin/repack.c: add cruft packs to MIDX during geometric repack, Taylor Blau
      • Re: [PATCH v4 15/17] builtin/repack.c: add cruft packs to MIDX during geometric repack, Ævar Arnfjörð Bjarmason
        • Re: [PATCH v4 15/17] builtin/repack.c: add cruft packs to MIDX during geometric repack, Taylor Blau
    • [PATCH v4 02/17] pack-mtimes: support reading .mtimes files, Taylor Blau
      • Re: [PATCH v4 02/17] pack-mtimes: support reading .mtimes files, Ævar Arnfjörð Bjarmason
        • Re: [PATCH v4 02/17] pack-mtimes: support reading .mtimes files, Junio C Hamano
          • Re: [PATCH v4 02/17] pack-mtimes: support reading .mtimes files, Ævar Arnfjörð Bjarmason
            • Re: [PATCH v4 02/17] pack-mtimes: support reading .mtimes files, Taylor Blau
    • [PATCH v4 06/17] t/helper: add 'pack-mtimes' test-tool, Taylor Blau
    • [PATCH v4 07/17] builtin/pack-objects.c: return from create_object_entry(), Taylor Blau
    • [PATCH v4 04/17] chunk-format.h: extract oid_version(), Taylor Blau
      • Re: [PATCH v4 04/17] chunk-format.h: extract oid_version(), Ævar Arnfjörð Bjarmason
    • [PATCH v4 01/17] Documentation/technical: add cruft-packs.txt, Taylor Blau
      • Re: [PATCH v4 01/17] Documentation/technical: add cruft-packs.txt, Junio C Hamano
    • [PATCH v4 10/17] reachable: report precise timestamps from objects in cruft packs, Taylor Blau
    • [PATCH v4 08/17] builtin/pack-objects.c: --cruft without expiration, Taylor Blau
      • Re: [PATCH v4 08/17] builtin/pack-objects.c: --cruft without expiration, Junio C Hamano
        • Re: [PATCH v4 08/17] builtin/pack-objects.c: --cruft without expiration, Junio C Hamano
          • Re: [PATCH v4 08/17] builtin/pack-objects.c: --cruft without expiration, Taylor Blau
    • [PATCH v4 03/17] pack-write: pass 'struct packing_data' to 'stage_tmp_packfiles', Taylor Blau
    • [PATCH v4 13/17] builtin/repack.c: allow configuring cruft pack generation, Taylor Blau
    • [PATCH v4 12/17] builtin/repack.c: support generating a cruft pack, Taylor Blau
      • Re: [PATCH v4 12/17] builtin/repack.c: support generating a cruft pack, Ævar Arnfjörð Bjarmason
        • Re: [PATCH v4 12/17] builtin/repack.c: support generating a cruft pack, Taylor Blau
    • [PATCH v4 14/17] builtin/repack.c: use named flags for existing_packs, Taylor Blau
    • [PATCH v4 09/17] reachable: add options to add_unseen_recent_objects_to_traversal, Taylor Blau
    • [PATCH v4 11/17] builtin/pack-objects.c: --cruft with expiration, Taylor Blau
    • [PATCH v4 05/17] pack-mtimes: support writing pack .mtimes files, Taylor Blau
    • [PATCH v4 16/17] builtin/gc.c: conditionally avoid pruning objects via loose, Taylor Blau
    • [PATCH v4 17/17] sha1-file.c: don't freshen cruft packs, Taylor Blau
    • Re: [PATCH v4 00/17] cruft packs, Derrick Stolee
      • Re: [PATCH v4 00/17] cruft packs, Junio C Hamano
        • Re: [PATCH v4 00/17] cruft packs, Taylor Blau
    • [RFC PATCH 0/2] Utility functions for duplicated pack(write) code, Ævar Arnfjörð Bjarmason
      • [RFC PATCH 2/2] hash API: add and use a hash_short_id_by_algo() function, Ævar Arnfjörð Bjarmason
        • Re: [RFC PATCH 2/2] hash API: add and use a hash_short_id_by_algo() function, Junio C Hamano
          • Re: [RFC PATCH 2/2] hash API: add and use a hash_short_id_by_algo() function, Ævar Arnfjörð Bjarmason
      • [RFC PATCH 1/2] packfile API: add and use a pack_name_to_ext() utility function, Ævar Arnfjörð Bjarmason
        • Re: [RFC PATCH 1/2] packfile API: add and use a pack_name_to_ext() utility function, Junio C Hamano
      • Re: [RFC PATCH 0/2] Utility functions for duplicated pack(write) code, Junio C Hamano
    • Re: [PATCH v4 00/17] cruft packs, Ævar Arnfjörð Bjarmason
  • [PATCH v5 00/17] cruft packs, Taylor Blau
    • [PATCH v5 04/17] chunk-format.h: extract oid_version(), Taylor Blau
    • [PATCH v5 02/17] pack-mtimes: support reading .mtimes files, Taylor Blau
      • Re: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files, Jonathan Nieder
        • RE: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files, rsbecker
          • Re: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files, Taylor Blau
            • RE: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files, rsbecker
              • Re: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files, Taylor Blau
                • RE: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files, rsbecker
                • adding new 32-bit on-disk (unsigned) timestamp formats (was: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files), Ævar Arnfjörð Bjarmason
                  • Re: adding new 32-bit on-disk (unsigned) timestamp formats (was: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files), Derrick Stolee
                    • Re: adding new 32-bit on-disk (unsigned) timestamp formats (was: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files), Taylor Blau
                      • Re: adding new 32-bit on-disk (unsigned) timestamp formats (was: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files), Ævar Arnfjörð Bjarmason
                        • Re: adding new 32-bit on-disk (unsigned) timestamp formats (was: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files), Taylor Blau
        • Re: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files, Taylor Blau
          • Re: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files, Jonathan Nieder
            • Re: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files, Taylor Blau
              • RE: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files, rsbecker
                • Re: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files, Taylor Blau
      • Re: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files, Taylor Blau
        • Re: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files, Junio C Hamano
      • Re: [PATCH v5 02/17] pack-mtimes: support reading .mtimes files, Andreas Schwab
    • [PATCH v5 05/17] pack-mtimes: support writing pack .mtimes files, Taylor Blau
    • [PATCH v5 10/17] reachable: report precise timestamps from objects in cruft packs, Taylor Blau
    • [PATCH v5 08/17] builtin/pack-objects.c: --cruft without expiration, Taylor Blau
    • [PATCH v5 06/17] t/helper: add 'pack-mtimes' test-tool, Taylor Blau
    • [PATCH v5 01/17] Documentation/technical: add cruft-packs.txt, Taylor Blau
    • [PATCH v5 07/17] builtin/pack-objects.c: return from create_object_entry(), Taylor Blau
    • [PATCH v5 09/17] reachable: add options to add_unseen_recent_objects_to_traversal, Taylor Blau
    • [PATCH v5 03/17] pack-write: pass 'struct packing_data' to 'stage_tmp_packfiles', Taylor Blau
    • [PATCH v5 12/17] builtin/repack.c: support generating a cruft pack, Taylor Blau
    • [PATCH v5 11/17] builtin/pack-objects.c: --cruft with expiration, Taylor Blau
    • [PATCH v5 13/17] builtin/repack.c: allow configuring cruft pack generation, Taylor Blau
    • [PATCH v5 15/17] builtin/repack.c: add cruft packs to MIDX during geometric repack, Taylor Blau
    • [PATCH v5 14/17] builtin/repack.c: use named flags for existing_packs, Taylor Blau
    • [PATCH v5 16/17] builtin/gc.c: conditionally avoid pruning objects via loose, Taylor Blau
      • Re: [PATCH v5 16/17] builtin/gc.c: conditionally avoid pruning objects via loose, René Scharfe
        • Re: [PATCH v5 16/17] builtin/gc.c: conditionally avoid pruning objects via loose, Junio C Hamano
    • [PATCH v5 17/17] sha1-file.c: don't freshen cruft packs, Taylor Blau
    • Re: [PATCH v5 00/17] cruft packs, Ævar Arnfjörð Bjarmason
      • Re: [PATCH v5 00/17] cruft packs, Jonathan Nieder
        • Re: [PATCH v5 00/17] cruft packs, Taylor Blau
          • Re: [PATCH v5 00/17] cruft packs, Ævar Arnfjörð Bjarmason
            • Re: [PATCH v5 00/17] cruft packs, Taylor Blau
              • Re: [PATCH v5 00/17] cruft packs, Jonathan Nieder
                • Re: [PATCH v5 00/17] cruft packs, Derrick Stolee
                  • Re: [PATCH v5 00/17] cruft packs, Taylor Blau
                    • Re: [PATCH v5 00/17] cruft packs, Ævar Arnfjörð Bjarmason
• [PATCH] grep: clarify what `grep.patternType=default` means, Junio C Hamano
  • Re: [PATCH] grep: clarify what `grep.patternType=default` means, Johannes Altmanninger
    • Re* [PATCH] grep: clarify what `grep.patternType=default` means, Junio C Hamano
      • [PATCH v2] grep: clarify what `grep.patternType=default` means, Junio C Hamano
• [PATCH 0/2] Set GIT_TRACE2_EVENT_NESTING in test-lib.sh, Derrick Stolee via GitGitGadget
  • [PATCH 1/2] test-lib.sh: set GIT_TRACE2_EVENT_NESTING, Derrick Stolee via GitGitGadget
    • Re: [PATCH 1/2] test-lib.sh: set GIT_TRACE2_EVENT_NESTING, Ævar Arnfjörð Bjarmason
      • Re: [PATCH 1/2] test-lib.sh: set GIT_TRACE2_EVENT_NESTING, Junio C Hamano
      • Re: [PATCH 1/2] test-lib.sh: set GIT_TRACE2_EVENT_NESTING, Junio C Hamano
  • [PATCH 2/2] t/t*: remove custom GIT_TRACE2_EVENT_NESTING, Derrick Stolee via GitGitGadget
  • Re: [PATCH 0/2] Set GIT_TRACE2_EVENT_NESTING in test-lib.sh, Jeff King
    • Re: [PATCH 0/2] Set GIT_TRACE2_EVENT_NESTING in test-lib.sh, Jeff King
      • Re: [PATCH 0/2] Set GIT_TRACE2_EVENT_NESTING in test-lib.sh, Taylor Blau
    • Re: [PATCH 0/2] Set GIT_TRACE2_EVENT_NESTING in test-lib.sh, Derrick Stolee
      • Re: [PATCH 0/2] Set GIT_TRACE2_EVENT_NESTING in test-lib.sh, Jeff Hostetler
        • Re: [PATCH 0/2] Set GIT_TRACE2_EVENT_NESTING in test-lib.sh, Jeff King
  • [PATCH] test-lib.sh: have all tests pass under "-x", remove BASH_XTRACEFD, Ævar Arnfjörð Bjarmason
    • Re: [PATCH] test-lib.sh: have all tests pass under "-x", remove BASH_XTRACEFD, Eric Sunshine
    • Re: [PATCH] test-lib.sh: have all tests pass under "-x", remove BASH_XTRACEFD, Jeff King
      • Re: [PATCH] test-lib.sh: have all tests pass under "-x", remove BASH_XTRACEFD, Ævar Arnfjörð Bjarmason
      • Re: [PATCH] test-lib.sh: have all tests pass under "-x", remove BASH_XTRACEFD, SZEDER Gábor
        • Re: [PATCH] test-lib.sh: have all tests pass under "-x", remove BASH_XTRACEFD, Ævar Arnfjörð Bjarmason
          • Re: [PATCH] test-lib.sh: have all tests pass under "-x", remove BASH_XTRACEFD, Jeff King
    • Re: [PATCH] test-lib.sh: have all tests pass under "-x", remove BASH_XTRACEFD, Junio C Hamano
    • [PATCH v2 0/2] test-lib.sh: have all tests pass under "-x", remove BASH_XTRACEFD, Ævar Arnfjörð Bjarmason
      • [PATCH v2 1/2] t1510: remove need for "test_untraceable", retain coverage, Ævar Arnfjörð Bjarmason
        • Re: [PATCH v2 1/2] t1510: remove need for "test_untraceable", retain coverage, SZEDER Gábor
          • Re: [PATCH v2 1/2] t1510: remove need for "test_untraceable", retain coverage, SZEDER Gábor
          • Re: [PATCH v2 1/2] t1510: remove need for "test_untraceable", retain coverage, Jeff King
            • Re: [PATCH v2 1/2] t1510: remove need for "test_untraceable", retain coverage, Ævar Arnfjörð Bjarmason
            • Re: [PATCH v2 1/2] t1510: remove need for "test_untraceable", retain coverage, SZEDER Gábor
      • [PATCH v2 2/2] test-lib.sh: remove the now-unused "test_untraceable" facility, Ævar Arnfjörð Bjarmason
      • [PATCH v3 0/2] test-lib.sh: have all tests pass under "-x", remove BASH_XTRACEFD, Ævar Arnfjörð Bjarmason
        • [PATCH v3 1/2] t1510: remove need for "test_untraceable", retain coverage, Ævar Arnfjörð Bjarmason
        • [PATCH v3 2/2] test-lib.sh: remove the now-unused "test_untraceable" facility, Ævar Arnfjörð Bjarmason
          • Re: [PATCH v3 2/2] test-lib.sh: remove the now-unused "test_untraceable" facility, SZEDER Gábor
            • Re: [PATCH v3 2/2] test-lib.sh: remove the now-unused "test_untraceable" facility, Ævar Arnfjörð Bjarmason
              • Re: [PATCH v3 2/2] test-lib.sh: remove the now-unused "test_untraceable" facility, SZEDER Gábor
                • Re: [PATCH v3 2/2] test-lib.sh: remove the now-unused "test_untraceable" facility, Junio C Hamano
                  • Re: [PATCH v3 2/2] test-lib.sh: remove the now-unused "test_untraceable" facility, Jeff King
                    • Re: [PATCH v3 2/2] test-lib.sh: remove the now-unused "test_untraceable" facility, Junio C Hamano
                      • Re: [PATCH v3 2/2] test-lib.sh: remove the now-unused "test_untraceable" facility, Jeff King
                        • Re: [PATCH v3 2/2] test-lib.sh: remove the now-unused "test_untraceable" facility, Junio C Hamano
                          • Re: [PATCH v3 2/2] test-lib.sh: remove the now-unused "test_untraceable" facility, Ævar Arnfjörð Bjarmason
        • [PATCH v4 0/3] test-lib.sh: have all tests pass under "-x", remove BASH_XTRACEFD, Ævar Arnfjörð Bjarmason
          • [PATCH v4 1/3] t1510: remove need for "test_untraceable", retain coverage, Ævar Arnfjörð Bjarmason
          • [PATCH v4 3/3] test-lib.sh: remove "BASH_XTRACEFD", Ævar Arnfjörð Bjarmason
            • Re: [PATCH v4 3/3] test-lib.sh: remove "BASH_XTRACEFD", SZEDER Gábor
              • Re: [PATCH v4 3/3] test-lib.sh: remove "BASH_XTRACEFD", Ævar Arnfjörð Bjarmason
          • [PATCH v4 2/3] test-lib.sh: remove the now-unused "test_untraceable" facility, Ævar Arnfjörð Bjarmason
          • Re: [PATCH v4 0/3] test-lib.sh: have all tests pass under "-x", remove BASH_XTRACEFD, SZEDER Gábor
            • Re: [PATCH v4 0/3] test-lib.sh: have all tests pass under "-x", remove BASH_XTRACEFD, Ævar Arnfjörð Bjarmason
              • Re: [PATCH v4 0/3] test-lib.sh: have all tests pass under "-x", remove BASH_XTRACEFD, SZEDER Gábor
                • Re: [PATCH v4 0/3] test-lib.sh: have all tests pass under "-x", remove BASH_XTRACEFD, Ævar Arnfjörð Bjarmason
• Hope all is well with you and your family!, Mr. Abderazack Zebdani
• [ANNOUNCE] Git Rev News edition 81, Christian Couder
• [PATCH] add -p: avoid use of undefined $key when ReadKey -> EOF, Carlo Marcelo Arenas Belón
  • Re: [PATCH] add -p: avoid use of undefined $key when ReadKey -> EOF, Junio C Hamano
    • Re: [PATCH] add -p: avoid use of undefined $key when ReadKey -> EOF, Carlo Arenas
      • Re: [PATCH] add -p: avoid use of undefined $key when ReadKey -> EOF, Junio C Hamano
• Git SSH/GPG signing flags and config, Fabian Stelzer
  • Re: Git SSH/GPG signing flags and config, Junio C Hamano
    • Re: Git SSH/GPG signing flags and config, Fabian Stelzer
• git diff -I<regex> does not work with empty +/- lines, Johannes Altmanninger
  • Re: git diff -I<regex> does not work with empty +/- lines, Junio C Hamano
    • Re: git diff -I<regex> does not work with empty +/- lines, Johannes Altmanninger
• [PATCH tig 0/2] Allow to toggle revision filter, Johannes Altmanninger
  • [PATCH tig 1/2] argv_format(): extract bool params into bitfield, Johannes Altmanninger
  • [PATCH tig 2/2] Allow to toggle revision filter, Johannes Altmanninger
• misleading message printed when worktree add fails, Baruch Burstein
  • Re: misleading message printed when worktree add fails, Eric Sunshine
    • Re: misleading message printed when worktree add fails, Baruch Burstein
      • Re: misleading message printed when worktree add fails, Eric Sunshine
        • RE: misleading message printed when worktree add fails, rsbecker
        • Re: misleading message printed when worktree add fails, Eric Sunshine
• Draft of Git Rev News edition 81, Christian Couder
• [ANNOUNCE] Git v2.34.1 NonStop Builds Available, rsbecker
• [BUG REPORT] `git rebase --exec` shouldn't run the exec command when there is nothing to rebase, Nikita Bobko
  • Re: [BUG REPORT] `git rebase --exec` shouldn't run the exec command when there is nothing to rebase, Ævar Arnfjörð Bjarmason
    • Re: [BUG REPORT] `git rebase --exec` shouldn't run the exec command when there is nothing to rebase, Elijah Newren
      • Re: [BUG REPORT] `git rebase --exec` shouldn't run the exec command when there is nothing to rebase, Taylor Blau
      • Re: [BUG REPORT] `git rebase --exec` shouldn't run the exec command when there is nothing to rebase, Elijah Newren
    • Re: [BUG REPORT] `git rebase --exec` shouldn't run the exec command when there is nothing to rebase, Phillip Wood
• Congratulations Dear. Beneficiary !!, Mr. Bill Gate
• [PATCH 0/4] Fix LLP64 `(size_t)1` compatibility VS C4334 warnings, Philip Oakley
  • [PATCH 1/4] mergesort.c: LLP64 compatibility, upcast unity for left shift, Philip Oakley
    • Re: [PATCH 1/4] mergesort.c: LLP64 compatibility, upcast unity for left shift, René Scharfe
      • Re: [PATCH 1/4] mergesort.c: LLP64 compatibility, upcast unity for left shift, Philip Oakley
  • [PATCH 4/4] object-file.c: LLP64 compatibility, upcast unity for left shift, Philip Oakley
  • [PATCH 3/4] diffcore-delta.c: LLP64 compatibility, upcast unity for left shift, Philip Oakley
    • Re: [PATCH 3/4] diffcore-delta.c: LLP64 compatibility, upcast unity for left shift, Derrick Stolee
      • Re: [PATCH 3/4] diffcore-delta.c: LLP64 compatibility, upcast unity for left shift, Philip Oakley
  • [PATCH 2/4] repack.c: LLP64 compatibility, upcast unity for left shift, Philip Oakley
    • Re: [PATCH 2/4] repack.c: LLP64 compatibility, upcast unity for left shift, Taylor Blau
      • Re: [PATCH 2/4] repack.c: LLP64 compatibility, upcast unity for left shift, Philip Oakley
  • Re: [PATCH 0/4] Fix LLP64 `(size_t)1` compatibility VS C4334 warnings, Derrick Stolee
• [PATCH] t1404: mark directory/file conflict tests with REFFILES, Han-Wen Nienhuys via GitGitGadget
  • Re: [PATCH] t1404: mark directory/file conflict tests with REFFILES, Junio C Hamano
    • Re: [PATCH] t1404: mark directory/file conflict tests with REFFILES, Han-Wen Nienhuys
      • Re: [PATCH] t1404: mark directory/file conflict tests with REFFILES, Junio C Hamano
  • [PATCH v2] t1404: mark directory/file conflict tests with REFFILES, Han-Wen Nienhuys via GitGitGadget
• [PATCH 0/2] Allow writing invalid OIDs into refs for testing purposes, Han-Wen Nienhuys via GitGitGadget
  • [PATCH 1/2] refs: update comment., Han-Wen Nienhuys via GitGitGadget
  • [PATCH 2/2] refs: allow skipping OID verification, Han-Wen Nienhuys via GitGitGadget
    • Re: [PATCH 2/2] refs: allow skipping OID verification, Junio C Hamano
  • [PATCH v2 0/6] Allow writing invalid OIDs into refs for testing purposes, Han-Wen Nienhuys via GitGitGadget
    • [PATCH v2 4/6] refs: add REF_SKIP_REFNAME_VERIFICATION flag, Han-Wen Nienhuys via GitGitGadget
      • Re: [PATCH v2 4/6] refs: add REF_SKIP_REFNAME_VERIFICATION flag, Junio C Hamano
      • Re: [PATCH v2 4/6] refs: add REF_SKIP_REFNAME_VERIFICATION flag, Junio C Hamano
        • Re: [PATCH v2 4/6] refs: add REF_SKIP_REFNAME_VERIFICATION flag, Han-Wen Nienhuys
          • Re: [PATCH v2 4/6] refs: add REF_SKIP_REFNAME_VERIFICATION flag, Junio C Hamano
            • Re: [PATCH v2 4/6] refs: add REF_SKIP_REFNAME_VERIFICATION flag, Jeff King
              • Re: [PATCH v2 4/6] refs: add REF_SKIP_REFNAME_VERIFICATION flag, Han-Wen Nienhuys
                • Re: [PATCH v2 4/6] refs: add REF_SKIP_REFNAME_VERIFICATION flag, Junio C Hamano
    • [PATCH v2 6/6] t1430: create valid symrefs using test-helper, Han-Wen Nienhuys via GitGitGadget
    • [PATCH v2 5/6] t1430: remove refs using test-tool, Han-Wen Nienhuys via GitGitGadget
    • [PATCH v2 1/6] test-ref-store: plug memory leak in cmd_delete_refs, Han-Wen Nienhuys via GitGitGadget
      • Re: [PATCH v2 1/6] test-ref-store: plug memory leak in cmd_delete_refs, Junio C Hamano
    • [PATCH v2 3/6] refs: allow skipping OID verification, Han-Wen Nienhuys via GitGitGadget
      • Re: [PATCH v2 3/6] refs: allow skipping OID verification, Junio C Hamano
    • [PATCH v2 2/6] refs: update comment., Han-Wen Nienhuys via GitGitGadget
      • Re: [PATCH v2 2/6] refs: update comment., Junio C Hamano
    • Re: [PATCH v2 0/6] Allow writing invalid OIDs into refs for testing purposes, Junio C Hamano
    • [PATCH v3 0/8] Allow writing invalid OIDs into refs for testing purposes, Han-Wen Nienhuys via GitGitGadget
      • [PATCH v3 1/8] test-ref-store: remove force-create argument for create-reflog, Han-Wen Nienhuys via GitGitGadget
      • [PATCH v3 2/8] test-ref-store: parse symbolic flag constants, Han-Wen Nienhuys via GitGitGadget
        • Re: [PATCH v3 2/8] test-ref-store: parse symbolic flag constants, Jeff King
      • [PATCH v3 3/8] test-ref-store: plug memory leak in cmd_delete_refs, Han-Wen Nienhuys via GitGitGadget
      • [PATCH v3 4/8] refs: update comment., Han-Wen Nienhuys via GitGitGadget
      • [PATCH v3 5/8] refs: introduce REF_SKIP_OID_VERIFICATION flag, Han-Wen Nienhuys via GitGitGadget
      • [PATCH v3 6/8] refs: introduce REF_SKIP_REFNAME_VERIFICATION flag, Han-Wen Nienhuys via GitGitGadget
      • [PATCH v3 7/8] t1430: remove refs using test-tool, Han-Wen Nienhuys via GitGitGadget
      • [PATCH v3 8/8] t1430: create valid symrefs using test-helper, Han-Wen Nienhuys via GitGitGadget
      • [PATCH v4 0/8] Allow writing invalid OIDs into refs for testing purposes, Han-Wen Nienhuys via GitGitGadget
        • [PATCH v4 1/8] test-ref-store: remove force-create argument for create-reflog, Han-Wen Nienhuys via GitGitGadget
        • [PATCH v4 2/8] test-ref-store: parse symbolic flag constants, Han-Wen Nienhuys via GitGitGadget
        • [PATCH v4 3/8] test-ref-store: plug memory leak in cmd_delete_refs, Han-Wen Nienhuys via GitGitGadget
        • [PATCH v4 4/8] refs: update comment., Han-Wen Nienhuys via GitGitGadget
        • [PATCH v4 5/8] refs: introduce REF_SKIP_OID_VERIFICATION flag, Han-Wen Nienhuys via GitGitGadget
        • [PATCH v4 6/8] refs: introduce REF_SKIP_REFNAME_VERIFICATION flag, Han-Wen Nienhuys via GitGitGadget
        • [PATCH v4 7/8] t1430: remove refs using test-tool, Han-Wen Nienhuys via GitGitGadget
        • [PATCH v4 8/8] t1430: create valid symrefs using test-helper, Han-Wen Nienhuys via GitGitGadget
        • Re: [PATCH v4 0/8] Allow writing invalid OIDs into refs for testing purposes, Junio C Hamano
• [PATCH] gitk: fix error when resizing gitk, Shulhan
  • Re: [PATCH] gitk: fix error when resizing gitk, Halil SEN
    • Re: [PATCH] gitk: fix error when resizing gitk, Shulhan
  • <Possible follow-ups>
  • [PATCH] gitk: fix error when resizing gitk, Shulhan
• [PATCH v2] Makefile: error out invoking strip target, Bagas Sanjaya
  • Re: [PATCH v2] Makefile: error out invoking strip target, Junio C Hamano
    • Re: [PATCH v2] Makefile: error out invoking strip target, Bagas Sanjaya
• [ANNOUNCE] Git for Windows 2.34.1, Johannes Schindelin
• [PATCH] githubci: add a workflow for creating GitHub release notes, Mahdi Hosseinzadeh via GitGitGadget
  • Re: [PATCH] githubci: add a workflow for creating GitHub release notes, Matthias Aßhauer
    • Re: [PATCH] githubci: add a workflow for creating GitHub release notes, Johannes Schindelin
      • Re: [PATCH] githubci: add a workflow for creating GitHub release notes, Matthias Aßhauer
        • Re: [PATCH] githubci: add a workflow for creating GitHub release notes, Ævar Arnfjörð Bjarmason
          • Re: [PATCH] githubci: add a workflow for creating GitHub release notes, Johannes Schindelin
            • Re: [PATCH] githubci: add a workflow for creating GitHub release notes, Junio C Hamano