Git Distributed Software Revision Control — Thread Index

• Date Index

• [PATCH 12/12] t7527: update case-insenstive fsmonitor test, (continued)
  • [PATCH 12/12] t7527: update case-insenstive fsmonitor test, Jeff Hostetler via GitGitGadget
  • [PATCH v2 00/16] FSMonitor edge cases on case-insensitive file systems, Jeff Hostetler via GitGitGadget
    • [PATCH v2 01/16] name-hash: add index_dir_find(), Jeff Hostetler via GitGitGadget
      • Re: [PATCH v2 01/16] name-hash: add index_dir_find(), Junio C Hamano
    • [PATCH v2 03/16] t7527: temporarily disable case-insensitive tests, Jeff Hostetler via GitGitGadget
      • Re: [PATCH v2 03/16] t7527: temporarily disable case-insensitive tests, Junio C Hamano
        • Re: [PATCH v2 03/16] t7527: temporarily disable case-insensitive tests, Jeff Hostetler
    • [PATCH v2 02/16] t7527: add case-insensitve test for FSMonitor, Jeff Hostetler via GitGitGadget
    • [PATCH v2 05/16] fsmonitor: clarify handling of directory events in callback helper, Jeff Hostetler via GitGitGadget
    • [PATCH v2 04/16] fsmonitor: refactor refresh callback on directory events, Jeff Hostetler via GitGitGadget
      • Re: [PATCH v2 04/16] fsmonitor: refactor refresh callback on directory events, Junio C Hamano
    • [PATCH v2 06/16] fsmonitor: refactor refresh callback for non-directory events, Jeff Hostetler via GitGitGadget
      • Re: [PATCH v2 06/16] fsmonitor: refactor refresh callback for non-directory events, Junio C Hamano
      • Re: [PATCH v2 06/16] fsmonitor: refactor refresh callback for non-directory events, Torsten Bögershausen
        • Re: [PATCH v2 06/16] fsmonitor: refactor refresh callback for non-directory events, Junio C Hamano
    • [PATCH v2 07/16] dir: create untracked_cache_invalidate_trimmed_path(), Jeff Hostetler via GitGitGadget
      • Re: [PATCH v2 07/16] dir: create untracked_cache_invalidate_trimmed_path(), Torsten Bögershausen
    • [PATCH v2 08/16] fsmonitor: refactor untracked-cache invalidation, Jeff Hostetler via GitGitGadget
    • [PATCH v2 09/16] fsmonitor: move untracked invalidation into helper functions, Jeff Hostetler via GitGitGadget
      • Re: [PATCH v2 09/16] fsmonitor: move untracked invalidation into helper functions, Junio C Hamano
        • Re: [PATCH v2 09/16] fsmonitor: move untracked invalidation into helper functions, Jeff Hostetler
    • [PATCH v2 10/16] fsmonitor: return invalidated cache-entry count on directory event, Jeff Hostetler via GitGitGadget
    • [PATCH v2 11/16] fsmonitor: remove custom loop from non-directory path handler, Jeff Hostetler via GitGitGadget
      • Re: [PATCH v2 11/16] fsmonitor: remove custom loop from non-directory path handler, Junio C Hamano
    • [PATCH v2 13/16] fsmonitor: trace the new invalidated cache-entry count, Jeff Hostetler via GitGitGadget
      • Re: [PATCH v2 13/16] fsmonitor: trace the new invalidated cache-entry count, Junio C Hamano
    • [PATCH v2 12/16] fsmonitor: return invalided cache-entry count on non-directory event, Jeff Hostetler via GitGitGadget
      • Re: [PATCH v2 12/16] fsmonitor: return invalided cache-entry count on non-directory event, Junio C Hamano
    • [PATCH v2 14/16] fsmonitor: support case-insensitive events, Jeff Hostetler via GitGitGadget
      • Re: [PATCH v2 14/16] fsmonitor: support case-insensitive events, Junio C Hamano
        • Re: [PATCH v2 14/16] fsmonitor: support case-insensitive events, Jeff Hostetler
          • Re: [PATCH v2 14/16] fsmonitor: support case-insensitive events, Junio C Hamano
      • Re: [PATCH v2 14/16] fsmonitor: support case-insensitive events, Torsten Bögershausen
        • Re: [PATCH v2 14/16] fsmonitor: support case-insensitive events, Jeff Hostetler
    • [PATCH v2 15/16] fsmonitor: refactor bit invalidation in refresh callback, Jeff Hostetler via GitGitGadget
      • Re: [PATCH v2 15/16] fsmonitor: refactor bit invalidation in refresh callback, Junio C Hamano
    • [PATCH v2 16/16] t7527: update case-insenstive fsmonitor test, Jeff Hostetler via GitGitGadget
    • [PATCH v3 00/14] FSMonitor edge cases on case-insensitive file systems, Jeff Hostetler via GitGitGadget
      • [PATCH v3 01/14] name-hash: add index_dir_find(), Jeff Hostetler via GitGitGadget
      • [PATCH v3 02/14] t7527: add case-insensitve test for FSMonitor, Jeff Hostetler via GitGitGadget
      • [PATCH v3 03/14] fsmonitor: refactor refresh callback on directory events, Jeff Hostetler via GitGitGadget
      • [PATCH v3 04/14] fsmonitor: clarify handling of directory events in callback helper, Jeff Hostetler via GitGitGadget
      • [PATCH v3 05/14] fsmonitor: refactor refresh callback for non-directory events, Jeff Hostetler via GitGitGadget
      • [PATCH v3 06/14] dir: create untracked_cache_invalidate_trimmed_path(), Jeff Hostetler via GitGitGadget
      • [PATCH v3 07/14] fsmonitor: refactor untracked-cache invalidation, Jeff Hostetler via GitGitGadget
      • [PATCH v3 08/14] fsmonitor: move untracked-cache invalidation into helper functions, Jeff Hostetler via GitGitGadget
      • [PATCH v3 09/14] fsmonitor: return invalidated cache-entry count on directory event, Jeff Hostetler via GitGitGadget
      • [PATCH v3 10/14] fsmonitor: remove custom loop from non-directory path handler, Jeff Hostetler via GitGitGadget
      • [PATCH v3 11/14] fsmonitor: return invalided cache-entry count on non-directory event, Jeff Hostetler via GitGitGadget
        • Re: [PATCH v3 11/14] fsmonitor: return invalided cache-entry count on non-directory event, Patrick Steinhardt
      • [PATCH v3 12/14] fsmonitor: trace the new invalidated cache-entry count, Jeff Hostetler via GitGitGadget
      • [PATCH v3 13/14] fsmonitor: refactor bit invalidation in refresh callback, Jeff Hostetler via GitGitGadget
      • [PATCH v3 14/14] fsmonitor: support case-insensitive events, Jeff Hostetler via GitGitGadget
        • Re: [PATCH v3 14/14] fsmonitor: support case-insensitive events, Patrick Steinhardt
      • Re: [PATCH v3 00/14] FSMonitor edge cases on case-insensitive file systems, Junio C Hamano
      • Re: [PATCH v3 00/14] FSMonitor edge cases on case-insensitive file systems, Patrick Steinhardt
        • Re: [PATCH v3 00/14] FSMonitor edge cases on case-insensitive file systems, Junio C Hamano
        • Re: [PATCH v3 00/14] FSMonitor edge cases on case-insensitive file systems, Jeff Hostetler
• [GSOC][RFC] microproject: use test_path_is_* functions in test scripts, Vincenzo MEZZELA
  • Re: [GSOC][RFC] microproject: use test_path_is_* functions in test scripts, Christian Couder
    • Re: [GSOC][RFC] microproject: use test_path_is_* functions in test scripts, Eric Sunshine
  • Re: [GSOC][RFC] microproject: use test_path_is_* functions in test scripts, Junio C Hamano
    • Re: [GSOC][RFC] microproject: use test_path_is_* functions in test scripts, vincenzo mezzela
• [PATCH 00/12] The merge-base logic vs missing commit objects, Johannes Schindelin via GitGitGadget
  • [PATCH 01/12] paint_down_to_common: plug a memory leak, Johannes Schindelin via GitGitGadget
  • [PATCH 03/12] Prepare `repo_in_merge_bases_many()` to optionally expect missing commits, Johannes Schindelin via GitGitGadget
  • [PATCH 02/12] Let `repo_in_merge_bases()` report missing commits, Johannes Schindelin via GitGitGadget
    • Re: [PATCH 02/12] Let `repo_in_merge_bases()` report missing commits, Patrick Steinhardt
  • [PATCH 05/12] commit-reach: start reporting errors in `paint_down_to_common()`, Johannes Schindelin via GitGitGadget
  • [PATCH 04/12] Prepare `paint_down_to_common()` for handling shallow commits, Johannes Schindelin via GitGitGadget
  • [PATCH 06/12] merge_bases_many(): pass on errors from `paint_down_to_common()`, Johannes Schindelin via GitGitGadget
  • [PATCH 07/12] get_merge_bases_many_0(): pass on errors from `merge_bases_many()`, Johannes Schindelin via GitGitGadget
  • [PATCH 08/12] repo_get_merge_bases(): pass on errors from `merge_bases_many()`, Johannes Schindelin via GitGitGadget
  • [PATCH 09/12] get_octopus_merge_bases(): pass on errors from `merge_bases_many()`, Johannes Schindelin via GitGitGadget
  • [PATCH 10/12] repo_get_merge_bases_many(): pass on errors from `merge_bases_many()`, Johannes Schindelin via GitGitGadget
  • [PATCH 11/12] repo_get_merge_bases_many_dirty(): pass on errors from `merge_bases_many()`, Johannes Schindelin via GitGitGadget
  • [PATCH 12/12] paint_down_to_common(): special-case shallow/partial clones, Johannes Schindelin via GitGitGadget
  • Re: [PATCH 00/12] The merge-base logic vs missing commit objects, Junio C Hamano
  • [PATCH v2 00/11] The merge-base logic vs missing commit objects, Johannes Schindelin via GitGitGadget
    • [PATCH v2 01/11] paint_down_to_common: plug two memory leaks, Johannes Schindelin via GitGitGadget
    • [PATCH v2 02/11] Prepare `repo_in_merge_bases_many()` to optionally expect missing commits, Johannes Schindelin via GitGitGadget
    • [PATCH v2 03/11] Start reporting missing commits in `repo_in_merge_bases_many()`, Johannes Schindelin via GitGitGadget
      • Re: [PATCH v2 03/11] Start reporting missing commits in `repo_in_merge_bases_many()`, Junio C Hamano
        • Re: [PATCH v2 03/11] Start reporting missing commits in `repo_in_merge_bases_many()`, Johannes Schindelin
          • Re: [PATCH v2 03/11] Start reporting missing commits in `repo_in_merge_bases_many()`, Junio C Hamano
      • Re: [PATCH v2 03/11] Start reporting missing commits in `repo_in_merge_bases_many()`, Jeff King
    • [PATCH v2 04/11] Prepare `paint_down_to_common()` for handling shallow commits, Johannes Schindelin via GitGitGadget
    • [PATCH v2 05/11] commit-reach: start reporting errors in `paint_down_to_common()`, Johannes Schindelin via GitGitGadget
    • [PATCH v2 06/11] merge_bases_many(): pass on errors from `paint_down_to_common()`, Johannes Schindelin via GitGitGadget
    • [PATCH v2 07/11] get_merge_bases_many_0(): pass on errors from `merge_bases_many()`, Johannes Schindelin via GitGitGadget
    • [PATCH v2 08/11] repo_get_merge_bases(): pass on errors from `merge_bases_many()`, Johannes Schindelin via GitGitGadget
    • [PATCH v2 10/11] repo_get_merge_bases_many(): pass on errors from `merge_bases_many()`, Johannes Schindelin via GitGitGadget
    • [PATCH v2 09/11] get_octopus_merge_bases(): pass on errors from `merge_bases_many()`, Johannes Schindelin via GitGitGadget
    • [PATCH v2 11/11] repo_get_merge_bases_many_dirty(): pass on errors from `merge_bases_many()`, Johannes Schindelin via GitGitGadget
    • [PATCH v3 00/11] The merge-base logic vs missing commit objects, Johannes Schindelin via GitGitGadget
      • [PATCH v3 01/11] paint_down_to_common: plug two memory leaks, Johannes Schindelin via GitGitGadget
      • [PATCH v3 02/11] Prepare `repo_in_merge_bases_many()` to optionally expect missing commits, Johannes Schindelin via GitGitGadget
      • [PATCH v3 03/11] Start reporting missing commits in `repo_in_merge_bases_many()`, Johannes Schindelin via GitGitGadget
      • [PATCH v3 05/11] commit-reach: start reporting errors in `paint_down_to_common()`, Johannes Schindelin via GitGitGadget
        • Re: [PATCH v3 05/11] commit-reach: start reporting errors in `paint_down_to_common()`, Dirk Gouders
          • Re: [PATCH v3 05/11] commit-reach: start reporting errors in `paint_down_to_common()`, Johannes Schindelin
            • Re: [PATCH v3 05/11] commit-reach: start reporting errors in `paint_down_to_common()`, Junio C Hamano
      • [PATCH v3 06/11] merge_bases_many(): pass on errors from `paint_down_to_common()`, Johannes Schindelin via GitGitGadget
        • Re: [PATCH v3 06/11] merge_bases_many(): pass on errors from `paint_down_to_common()`, Junio C Hamano
      • [PATCH v3 07/11] get_merge_bases_many_0(): pass on errors from `merge_bases_many()`, Johannes Schindelin via GitGitGadget
      • [PATCH v3 08/11] repo_get_merge_bases(): pass on errors from `merge_bases_many()`, Johannes Schindelin via GitGitGadget
      • [PATCH v3 09/11] get_octopus_merge_bases(): pass on errors from `merge_bases_many()`, Johannes Schindelin via GitGitGadget
      • [PATCH v3 10/11] repo_get_merge_bases_many(): pass on errors from `merge_bases_many()`, Johannes Schindelin via GitGitGadget
      • [PATCH v3 04/11] Prepare `paint_down_to_common()` for handling shallow commits, Johannes Schindelin via GitGitGadget
        • Re: [PATCH v3 04/11] Prepare `paint_down_to_common()` for handling shallow commits, Dirk Gouders
          • Re: [PATCH v3 04/11] Prepare `paint_down_to_common()` for handling shallow commits, Johannes Schindelin
            • Re: [PATCH v3 04/11] Prepare `paint_down_to_common()` for handling shallow commits, Junio C Hamano
              • Re: [PATCH v3 04/11] Prepare `paint_down_to_common()` for handling shallow commits, Junio C Hamano
              • Re: [PATCH v3 04/11] Prepare `paint_down_to_common()` for handling shallow commits, Dirk Gouders
      • [PATCH v3 11/11] repo_get_merge_bases_many_dirty(): pass on errors from `merge_bases_many()`, Johannes Schindelin via GitGitGadget
      • [PATCH v4 00/11] The merge-base logic vs missing commit objects, Johannes Schindelin via GitGitGadget
        • [PATCH v4 01/11] commit-reach(paint_down_to_common): plug two memory leaks, Johannes Schindelin via GitGitGadget
        • [PATCH v4 02/11] commit-reach(repo_in_merge_bases_many): optionally expect missing commits, Johannes Schindelin via GitGitGadget
        • [PATCH v4 04/11] commit-reach(paint_down_to_common): prepare for handling shallow commits, Johannes Schindelin via GitGitGadget
          • Re: [PATCH v4 04/11] commit-reach(paint_down_to_common): prepare for handling shallow commits, Junio C Hamano
            • Re: [PATCH v4 04/11] commit-reach(paint_down_to_common): prepare for handling shallow commits, Dirk Gouders
              • Re: [PATCH v4 04/11] commit-reach(paint_down_to_common): prepare for handling shallow commits, Johannes Schindelin
            • Re: [PATCH v4 04/11] commit-reach(paint_down_to_common): prepare for handling shallow commits, Johannes Schindelin
        • [PATCH v4 03/11] commit-reach(repo_in_merge_bases_many): report missing commits, Johannes Schindelin via GitGitGadget
          • Re: [PATCH v4 03/11] commit-reach(repo_in_merge_bases_many): report missing commits, Jeff King
            • Re: [PATCH v4 03/11] commit-reach(repo_in_merge_bases_many): report missing commits, Junio C Hamano
        • [PATCH v4 05/11] commit-reach(paint_down_to_common): start reporting errors, Johannes Schindelin via GitGitGadget
        • [PATCH v4 06/11] commit-reach(merge_bases_many): pass on "missing commits" errors, Johannes Schindelin via GitGitGadget
        • [PATCH v4 08/11] commit-reach(repo_get_merge_bases): pass on "missing commits" errors, Johannes Schindelin via GitGitGadget
        • [PATCH v4 07/11] commit-reach(get_merge_bases_many_0): pass on "missing commits" errors, Johannes Schindelin via GitGitGadget
        • [PATCH v4 10/11] commit-reach(repo_get_merge_bases_many): pass on "missing commits" errors, Johannes Schindelin via GitGitGadget
        • [PATCH v4 11/11] commit-reach(repo_get_merge_bases_many_dirty): pass on errors, Johannes Schindelin via GitGitGadget
        • [PATCH v4 09/11] commit-reach(get_octopus_merge_bases): pass on "missing commits" errors, Johannes Schindelin via GitGitGadget
• Possible bug with 'diff --cc' report, Groboclown
• Bug report: Incorrect GIT_FLUSH behavior in 2.43.1 (regression and breaking), Xiaoguang WANG
  • Re: Bug report: Incorrect GIT_FLUSH behavior in 2.43.1 (regression and breaking), Junio C Hamano
    • Re: Bug report: Incorrect GIT_FLUSH behavior in 2.43.1 (regression and breaking), Xiaoguang WANG
    • Re: Bug report: Incorrect GIT_FLUSH behavior in 2.43.1 (regression and breaking), Phillip Wood
      • Re: Bug report: Incorrect GIT_FLUSH behavior in 2.43.1 (regression and breaking), Junio C Hamano
        • Re: Bug report: Incorrect GIT_FLUSH behavior in 2.43.1 (regression and breaking), Junio C Hamano
          • Re: Bug report: Incorrect GIT_FLUSH behavior in 2.43.1 (regression and breaking), Phillip Wood
• Bids Take-off, gonzalezterrell618
• Bug: git-subtree: splitting subtree fails when subtree was added, removed and added again, tionis
• [PATCH] t9146: replace test -d/-f with appropriate test_path_is_* function, Chandra Pratap via GitGitGadget
  • Re: [PATCH] t9146: replace test -d/-f with appropriate test_path_is_* function, Eric Sunshine
  • [PATCH v2] t9146: replace test -d/-e/-f with appropriate test_path_is_* function, Chandra Pratap via GitGitGadget
    • Re: [PATCH v2] t9146: replace test -d/-e/-f with appropriate test_path_is_* function, Junio C Hamano
    • [PATCH v3] t9146: replace test -d/-e/-f with appropriate test_path_is_* function, Chandra Pratap via GitGitGadget
• [PATCH] ci: bump remaining outdated Actions versions, Johannes Schindelin via GitGitGadget
  • [PATCH v2 0/2] ci: bump remaining outdated Actions versions, Johannes Schindelin via GitGitGadget
    • [PATCH v2 1/2] ci: bump remaining outdated Actions versions, Johannes Schindelin via GitGitGadget
    • [PATCH v2 2/2] ci(linux32): add a note about Actions that must not be updated, Johannes Schindelin via GitGitGadget
      • Re: [PATCH v2 2/2] ci(linux32): add a note about Actions that must not be updated, Junio C Hamano
  • Re: [PATCH] ci: bump remaining outdated Actions versions, Junio C Hamano
    • Re: [PATCH] ci: bump remaining outdated Actions versions, Junio C Hamano
• [PATCH] unit-tests: do show relative file paths on non-Windows, too, Junio C Hamano
  • Re: [PATCH] unit-tests: do show relative file paths on non-Windows, too, Phillip Wood
    • [PATCH v2] unit-tests: do show relative file paths on non-Windows, too, Junio C Hamano
      • Re: [PATCH v2] unit-tests: do show relative file paths on non-Windows, too, Phillip Wood
        • Re: [PATCH v2] unit-tests: do show relative file paths on non-Windows, too, Junio C Hamano
          • Re: [PATCH v2] unit-tests: do show relative file paths on non-Windows, too, Phillip Wood
            • Re: [PATCH v2] unit-tests: do show relative file paths on non-Windows, too, Junio C Hamano
      • Re: [PATCH v2] unit-tests: do show relative file paths on non-Windows, too, Johannes Schindelin
        • Re: [PATCH v2] unit-tests: do show relative file paths on non-Windows, too, Junio C Hamano
• git gc changes ownerships of files linux, K_V
  • Re: git gc changes ownerships of files linux, Torsten Bögershausen
    • Re: git gc changes ownerships of files linux, brian m. carlson
      • Re: git gc changes ownerships of files linux, Torsten Bögershausen
        • Re: git gc changes ownerships of files linux, Junio C Hamano
          • Re: git gc changes ownerships of files linux, Torsten Bögershausen
          • Re: git gc changes ownerships of files linux, brian m. carlson
            • RE: git gc changes ownerships of files linux, rsbecker
• [BUG] git 2.44.0-rc0 t0080.1 Breaks on NonStop x86 and ia64, rsbecker
  • RE: [BUG] git 2.44.0-rc0 t0080.1 Breaks on NonStop x86 and ia64, rsbecker
  • Re: [BUG] git 2.44.0-rc0 t0080.1 Breaks on NonStop x86 and ia64, Junio C Hamano
    • RE: [BUG] git 2.44.0-rc0 t0080.1 Breaks on NonStop x86 and ia64, rsbecker
      • RE: [BUG] git 2.44.0-rc0 t0080.1 Breaks on NonStop x86 and ia64, rsbecker
        • Re: [BUG] git 2.44.0-rc0 t0080.1 Breaks on NonStop x86 and ia64, Junio C Hamano
          • RE: [BUG] git 2.44.0-rc0 t0080.1 Breaks on NonStop x86 and ia64, rsbecker
            • Re: [BUG] git 2.44.0-rc0 t0080.1 Breaks on NonStop x86 and ia64, Junio C Hamano
              • RE: [BUG] git 2.44.0-rc0 t0080.1 Breaks on NonStop x86 and ia64, rsbecker
• [L10N] Kickoff for Git 2.44.0 round #1, Jiang Xin
  • Re: [L10N] Kickoff for Git 2.44.0 round #1, Junio C Hamano
• [ANNOUNCE] Git for Windows 2.44.0-rc0, Johannes Schindelin
  • Re: [ANNOUNCE] Git for Windows 2.44.0-rc0, Junio C Hamano
• Open Apple Store, Ashok Sharma
• [PATCH] use xstrncmpz(), René Scharfe
• git status became very slow after upgrading git, Vijay Raghavan Aravamudhan
  • Re: git status became very slow after upgrading git, Sean Allred
    • Re: git status became very slow after upgrading git, Vijay Raghavan Aravamudhan
      • Re: git status became very slow after upgrading git, Sean Allred
        • Re: git status became very slow after upgrading git, Vijay Raghavan Aravamudhan
• [PATCH 1/2] receive-pack: use find_commit_header() in check_cert_push_options(), René Scharfe
  • [PATCH 2/2] receive-pack: use find_commit_header() in check_nonce(), René Scharfe
    • Re: [PATCH 2/2] receive-pack: use find_commit_header() in check_nonce(), Junio C Hamano
    • [PATCH 3/2] commit: remove find_header_mem(), René Scharfe
      • Re: [PATCH 3/2] commit: remove find_header_mem(), Jeff King
        • Re: [PATCH 3/2] commit: remove find_header_mem(), Junio C Hamano
  • Re: [PATCH 1/2] receive-pack: use find_commit_header() in check_cert_push_options(), Junio C Hamano
    • Re: [PATCH 1/2] receive-pack: use find_commit_header() in check_cert_push_options(), René Scharfe
      • Re: [PATCH 1/2] receive-pack: use find_commit_header() in check_cert_push_options(), Junio C Hamano
• [ANNOUNCE] Git v2.44.0-rc0, Junio C Hamano
• [ANNOUNCE] Git v2.43.1, Junio C Hamano
• What's cooking in git.git (Feb 2024, #04; Thu, 8), Junio C Hamano
  • Re: What's cooking in git.git (Feb 2024, #04; Thu, 8), Philippe Blain
    • Re: What's cooking in git.git (Feb 2024, #04; Thu, 8), Junio C Hamano
• Interactive rebase: using "pick" for merge commits, Stefan Haller
  • Re: Interactive rebase: using "pick" for merge commits, Phillip Wood
    • Re: Interactive rebase: using "pick" for merge commits, Stefan Haller
      • Re: Interactive rebase: using "pick" for merge commits, Patrick Steinhardt
        • Re: Interactive rebase: using "pick" for merge commits, Phillip Wood
          • Re: Interactive rebase: using "pick" for merge commits, Stefan Haller
            • Re: Interactive rebase: using "pick" for merge commits, Phillip Wood
              • Re: Interactive rebase: using "pick" for merge commits, Stefan Haller
                • Re: Interactive rebase: using "pick" for merge commits, phillip . wood123
        • Re: Interactive rebase: using "pick" for merge commits, Junio C Hamano
• git column fails (or crashes) if padding is negative, Tiago Pascoal
  • Re: git column fails (or crashes) if padding is negative, Kristoffer Haugsbakk
    • Re: git column fails (or crashes) if padding is negative, Junio C Hamano
      • Re: git column fails (or crashes) if padding is negative, Kristoffer Haugsbakk
        • Re: git column fails (or crashes) if padding is negative, Junio C Hamano
  • [PATCH] column: disallow negative padding, Kristoffer Haugsbakk
    • Re: [PATCH] column: disallow negative padding, Kristoffer Haugsbakk
      • Re: [PATCH] column: disallow negative padding, Chris Torek
        • Re: [PATCH] column: disallow negative padding, Kristoffer Haugsbakk
          • Re: [PATCH] column: disallow negative padding, Junio C Hamano
            • Re: [PATCH] column: disallow negative padding, Kristoffer Haugsbakk
    • [PATCH v2] column: disallow negative padding, Kristoffer Haugsbakk
      • Re: [PATCH v2] column: disallow negative padding, Rubén Justo
        • Re: [PATCH v2] column: disallow negative padding, Rubén Justo
        • Re: [PATCH v2] column: disallow negative padding, Kristoffer Haugsbakk
        • Re: [PATCH v2] column: disallow negative padding, Kristoffer Haugsbakk
          • Re: [PATCH v2] column: disallow negative padding, Rubén Justo
      • [PATCH v3 0/2] column: disallow negative padding, Kristoffer Haugsbakk
        • [PATCH v3 1/2] column: disallow negative padding, Kristoffer Haugsbakk
        • [PATCH v3 2/2] column: guard against negative padding, Kristoffer Haugsbakk
          • Re: [PATCH v3 2/2] column: guard against negative padding, Junio C Hamano
            • Re: [PATCH v3 2/2] column: guard against negative padding, Rubén Justo
              • Re: [PATCH v3 2/2] column: guard against negative padding, Junio C Hamano
                • Re: [PATCH v3 2/2] column: guard against negative padding, Rubén Justo
                  • Re: [PATCH v3 2/2] column: guard against negative padding, Kristoffer Haugsbakk
                    • Re: [PATCH v3 2/2] column: guard against negative padding, Junio C Hamano
                • Re: [PATCH v3 2/2] column: guard against negative padding, Rubén Justo
                  • [PATCH] tag: error when git-column fails, Rubén Justo
                    • Re: [PATCH] tag: error when git-column fails, Junio C Hamano
        • Re: [PATCH v3 0/2] column: disallow negative padding, Rubén Justo
          • Re: [PATCH v3 0/2] column: disallow negative padding, Kristoffer Haugsbakk
            • Re: [PATCH v3 0/2] column: disallow negative padding, Junio C Hamano
• Race condition in git-bundle(1) create when ref is updated while running, Toon Claes
  • Re: Race condition in git-bundle(1) create when ref is updated while running, Junio C Hamano
    • Re: Race condition in git-bundle(1) create when ref is updated while running, Patrick Steinhardt
• [PATCH] doc: git.txt-Fix inconsistency param description, 秃头灯笼鱼 via GitGitGadget
  • [PATCH v2 0/2] Fix the inconsistency in the description of the namespace option's parameter, 秃头灯笼鱼 via GitGitGadget
    • [PATCH v2 1/2] doc: git.txt-Fix inconsistency param description, 秃头灯笼鱼 via GitGitGadget
      • Re: [PATCH v2 1/2] doc: git.txt-Fix inconsistency param description, Martin Ågren
        • Re: [PATCH v2 1/2] doc: git.txt-Fix inconsistency param description, Junio C Hamano
        • Re:Re: [PATCH v2 1/2] doc: git.txt-Fix inconsistency param description, ttdlyu
    • [PATCH v2 2/2] doc: git.txt-Change "--user-formats" to "--user-interfaces", 秃头灯笼鱼 via GitGitGadget
      • Re: [PATCH v2 2/2] doc: git.txt-Change "--user-formats" to "--user-interfaces", Junio C Hamano
        • Re:Re: [PATCH v2 2/2] doc: git.txt-Change "--user-formats" to "--user-interfaces", ttdlyu
          • Re: [PATCH v2 2/2] doc: git.txt-Change "--user-formats" to "--user-interfaces", Junio C Hamano
• [PATCH 0/7] t: drop more REFFILES prereqs, Patrick Steinhardt
  • [PATCH 1/7] t: move tests exercising the "files" backend, Patrick Steinhardt
    • Re: [PATCH 1/7] t: move tests exercising the "files" backend, Junio C Hamano
  • [PATCH 2/7] t0410: enable tests with extensions with non-default repo format, Patrick Steinhardt
    • Re: [PATCH 2/7] t0410: enable tests with extensions with non-default repo format, Junio C Hamano
      • Re: [PATCH 2/7] t0410: enable tests with extensions with non-default repo format, Patrick Steinhardt
        • Re: [PATCH 2/7] t0410: enable tests with extensions with non-default repo format, Junio C Hamano
  • [PATCH 3/7] t1400: exercise reflog with gaps with reftable backend, Patrick Steinhardt
    • Re: [PATCH 3/7] t1400: exercise reflog with gaps with reftable backend, Junio C Hamano
  • [PATCH 4/7] t1404: make D/F conflict tests compatible with reftable backend, Patrick Steinhardt
    • Re: [PATCH 4/7] t1404: make D/F conflict tests compatible with reftable backend, Junio C Hamano
  • [PATCH 5/7] t1405: remove unneeded cleanup step, Patrick Steinhardt
    • Re: [PATCH 5/7] t1405: remove unneeded cleanup step, Junio C Hamano
      • Re: [PATCH 5/7] t1405: remove unneeded cleanup step, Patrick Steinhardt
  • [PATCH 6/7] t2011: exercise D/F conflicts with HEAD with the reftable backend, Patrick Steinhardt
  • [PATCH 7/7] t7003: ensure filter-branch prunes reflogs with the reftable backend, Patrick Steinhardt
  • Re: [PATCH 0/7] t: drop more REFFILES prereqs, Karthik Nayak
  • Re: [PATCH 0/7] t: drop more REFFILES prereqs, Junio C Hamano
    • Re: [PATCH 0/7] t: drop more REFFILES prereqs, Patrick Steinhardt
  • [PATCH v2 0/7] t: drop more REFFILES prereqs, Patrick Steinhardt
    • [PATCH v2 1/7] t: move tests exercising the "files" backend, Patrick Steinhardt
    • [PATCH v2 2/7] t0410: convert tests to use DEFAULT_REPO_FORMAT prereq, Patrick Steinhardt
      • Re: [PATCH v2 2/7] t0410: convert tests to use DEFAULT_REPO_FORMAT prereq, Junio C Hamano
    • [PATCH v2 3/7] t1400: exercise reflog with gaps with reftable backend, Patrick Steinhardt
    • [PATCH v2 4/7] t1404: make D/F conflict tests compatible with reftable backend, Patrick Steinhardt
    • [PATCH v2 5/7] t1405: remove unneeded cleanup step, Patrick Steinhardt
    • [PATCH v2 6/7] t2011: exercise D/F conflicts with HEAD with the reftable backend, Patrick Steinhardt
    • [PATCH v2 7/7] t7003: ensure filter-branch prunes reflogs with the reftable backend, Patrick Steinhardt
• libification: how to avoid symbol collisions?, Kyle Lippincott
  • RE: libification: how to avoid symbol collisions?, rsbecker
    • Re: libification: how to avoid symbol collisions?, Kyle Lippincott
  • Re: libification: how to avoid symbol collisions?, Junio C Hamano
    • Re: libification: how to avoid symbol collisions?, Kyle Lippincott
      • Re: libification: how to avoid symbol collisions?, Junio C Hamano
• [PATCH] git: --no-lazy-fetch option, Junio C Hamano
  • Re: [PATCH] git: --no-lazy-fetch option, Linus Arver
    • Re: [PATCH] git: --no-lazy-fetch option, Linus Arver
      • Re: [PATCH] git: --no-lazy-fetch option, Junio C Hamano
  • Re: [PATCH] git: --no-lazy-fetch option, Jeff King
    • Re: [PATCH] git: --no-lazy-fetch option, Junio C Hamano
      • Re: [PATCH] git: --no-lazy-fetch option, Junio C Hamano
        • [PATCH] git: extend --no-lazy-fetch to work across subprocesses, Junio C Hamano
          • Re: [PATCH] git: extend --no-lazy-fetch to work across subprocesses, Linus Arver
            • Re: [PATCH] git: extend --no-lazy-fetch to work across subprocesses, Junio C Hamano
              • Re: [PATCH] git: extend --no-lazy-fetch to work across subprocesses, Linus Arver
          • Re: [PATCH] git: extend --no-lazy-fetch to work across subprocesses, Jeff King
            • Re: [PATCH] git: extend --no-lazy-fetch to work across subprocesses, Junio C Hamano
              • Re: [PATCH] git: extend --no-lazy-fetch to work across subprocesses, Jeff King
                • Re: [PATCH] git: extend --no-lazy-fetch to work across subprocesses, Junio C Hamano
                  • Re: [PATCH] git: extend --no-lazy-fetch to work across subprocesses, Jeff King
                    • Re: [PATCH] git: extend --no-lazy-fetch to work across subprocesses, Junio C Hamano
        • Re: [PATCH] git: --no-lazy-fetch option, Jeff King
          • Re: [PATCH] git: --no-lazy-fetch option, Linus Arver
    • Re: [PATCH] git: --no-lazy-fetch option, Linus Arver
• cloning the linxu kernel repo at a VPS with small RAM, Toralf Förster
  • Re: cloning the linxu kernel repo at a VPS with small RAM, Dragan Simic
    • Re: cloning the linxu kernel repo at a VPS with small RAM, Dragan Simic
  • Re: cloning the linxu kernel repo at a VPS with small RAM, Eric Wong
  • Re: cloning the linxu kernel repo at a VPS with small RAM, Toralf Förster
• [PATCH] prune: mark rebase autostash and orig-head as reachable, Phillip Wood via GitGitGadget
  • Re: [PATCH] prune: mark rebase autostash and orig-head as reachable, Eric Sunshine
    • Re: [PATCH] prune: mark rebase autostash and orig-head as reachable, Phillip Wood
  • Re: [PATCH] prune: mark rebase autostash and orig-head as reachable, Junio C Hamano
    • Re: [PATCH] prune: mark rebase autostash and orig-head as reachable, Phillip Wood
    • Re: [PATCH] prune: mark rebase autostash and orig-head as reachable, Phil Hord
  • [PATCH v2] prune: mark rebase autostash and orig-head as reachable, Phillip Wood via GitGitGadget
    • Re: [PATCH v2] prune: mark rebase autostash and orig-head as reachable, Junio C Hamano
• Bug: Commit fails when no global email address is set even though --author is used, Marcus Tillmanns
  • Re: Bug: Commit fails when no global email address is set even though --author is used, Phillip Wood
    • Re: Bug: Commit fails when no global email address is set even though --author is used, Marcus Tillmanns
      • Re: Bug: Commit fails when no global email address is set even though --author is used, Konstantin Khomoutov
      • Re: Bug: Commit fails when no global email address is set even though --author is used, Kristoffer Haugsbakk
        • Re: Bug: Commit fails when no global email address is set even though --author is used, Marcus Tillmanns
          • Re: Bug: Commit fails when no global email address is set even though --author is used, Kristoffer Haugsbakk
            • Re: Bug: Commit fails when no global email address is set even though --author is used, Junio C Hamano
              • Re: Bug: Commit fails when no global email address is set even though --author is used, Kristoffer Haugsbakk
                • Re: Bug: Commit fails when no global email address is set even though --author is used, Junio C Hamano
                  • Re: Bug: Commit fails when no global email address is set even though --author is used, Marcus Tillmanns
                    • Re: Bug: Commit fails when no global email address is set even though --author is used, Junio C Hamano
                  • Re: Bug: Commit fails when no global email address is set even though --author is used, Kristoffer Haugsbakk
• [PATCH v2 0/4] rev-list: allow missing tips with --missing, Christian Couder
  • [PATCH v2 1/4] revision: clarify a 'return NULL' in get_reference(), Christian Couder
  • [PATCH v2 2/4] oidset: refactor oidset_insert_from_set(), Christian Couder
    • Re: [PATCH v2 2/4] oidset: refactor oidset_insert_from_set(), Junio C Hamano
    • Re: [PATCH v2 2/4] oidset: refactor oidset_insert_from_set(), Linus Arver
      • Re: [PATCH v2 2/4] oidset: refactor oidset_insert_from_set(), Christian Couder
        • Re: [PATCH v2 2/4] oidset: refactor oidset_insert_from_set(), Linus Arver
          • Re: [PATCH v2 2/4] oidset: refactor oidset_insert_from_set(), Christian Couder
            • Re: [PATCH v2 2/4] oidset: refactor oidset_insert_from_set(), Linus Arver
  • [PATCH v2 3/4] t6022: fix 'test' style and 'even though' typo, Christian Couder
  • [PATCH v2 4/4] rev-list: allow missing tips with --missing=[print|allow*], Christian Couder
    • Re: [PATCH v2 4/4] rev-list: allow missing tips with --missing=[print|allow*], Junio C Hamano
      • Re: [PATCH v2 4/4] rev-list: allow missing tips with --missing=[print|allow*], Linus Arver
        • Re: [PATCH v2 4/4] rev-list: allow missing tips with --missing=[print|allow*], Christian Couder
          • Re: [PATCH v2 4/4] rev-list: allow missing tips with --missing=[print|allow*], Junio C Hamano
      • Re: [PATCH v2 4/4] rev-list: allow missing tips with --missing=[print|allow*], Christian Couder
    • Re: [PATCH v2 4/4] rev-list: allow missing tips with --missing=[print|allow*], Linus Arver
      • Re: [PATCH v2 4/4] rev-list: allow missing tips with --missing=[print|allow*], Christian Couder
        • Re: [PATCH v2 4/4] rev-list: allow missing tips with --missing=[print|allow*], Linus Arver
  • Re: [PATCH v2 0/4] rev-list: allow missing tips with --missing, Junio C Hamano
    • Re: [PATCH v2 0/4] rev-list: allow missing tips with --missing, Christian Couder
  • [PATCH v3 0/5] rev-list: allow missing tips with --missing, Christian Couder
    • [PATCH v3 1/5] t9210: do not rely on lazy fetching to fail, Christian Couder
    • [PATCH v3 2/5] revision: clarify a 'return NULL' in get_reference(), Christian Couder
    • [PATCH v3 3/5] oidset: refactor oidset_insert_from_set(), Christian Couder
    • [PATCH v3 4/5] t6022: fix 'test' style and 'even though' typo, Christian Couder
    • [PATCH v3 5/5] rev-list: allow missing tips with --missing=[print|allow*], Christian Couder
    • Re: [PATCH v3 0/5] rev-list: allow missing tips with --missing, Linus Arver
    • [PATCH] revision: fix --missing=[print|allow*] for annotated tags, Christian Couder
      • Re: [PATCH] revision: fix --missing=[print|allow*] for annotated tags, Junio C Hamano
• [PATCH] refs/reftable: fix leak when copying reflog fails, Patrick Steinhardt
  • Re: [PATCH] refs/reftable: fix leak when copying reflog fails, Jeff King
• [PATCH] ref-filter.c: sort formatted dates by byte value, Victoria Dye via GitGitGadget
  • Re: [PATCH] ref-filter.c: sort formatted dates by byte value, Junio C Hamano
    • Re: [PATCH] ref-filter.c: sort formatted dates by byte value, Victoria Dye
      • Re: [PATCH] ref-filter.c: sort formatted dates by byte value, Junio C Hamano
• Interest in options for stash -k and -u by default, Ricardo C
  • Re: Interest in options for stash -k and -u by default, Junio C Hamano
  • Re: Interest in options for stash -k and -u by default, Kristoffer Haugsbakk
• git gc destroys autostash, Orgad Shaneh
  • Re: git gc destroys autostash, Junio C Hamano
  • Re: git gc destroys autostash, Kristoffer Haugsbakk
• Supporting --no-edit for git rebase --continue, Orgad Shaneh
  • Re: Supporting --no-edit for git rebase --continue, brian m. carlson
    • Re: Supporting --no-edit for git rebase --continue, Orgad Shaneh
  • Re: Supporting --no-edit for git rebase --continue, Phillip Wood
• [PATCH] tag: fix sign_buffer() call to create a signed tag, Junio C Hamano
  • Re: [PATCH] tag: fix sign_buffer() call to create a signed tag, Jeff King
    • Re: [PATCH] tag: fix sign_buffer() call to create a signed tag, Junio C Hamano
      • Re: [PATCH] tag: fix sign_buffer() call to create a signed tag, Junio C Hamano
        • Re: [PATCH] tag: fix sign_buffer() call to create a signed tag, Jeff King
      • Re: [PATCH] tag: fix sign_buffer() call to create a signed tag, Jeff King
• [RFH] "git -C there add foo" completes, s/add/diff/ does not, Junio C Hamano
  • Re: [RFH] "git -C there add foo" completes, s/add/diff/ does not, Kyle Lippincott
    • Re: [RFH] "git -C there add foo" completes, s/add/diff/ does not, Junio C Hamano
• [PATCH 0/2] show-ref --verify: accept psuedorefs, Phillip Wood via GitGitGadget
  • [PATCH 1/2] show-ref --verify: accept pseudorefs, Phillip Wood via GitGitGadget
    • Re: [PATCH 1/2] show-ref --verify: accept pseudorefs, Junio C Hamano
      • Re: [PATCH 1/2] show-ref --verify: accept pseudorefs, Patrick Steinhardt
      • Re: [PATCH 1/2] show-ref --verify: accept pseudorefs, phillip . wood123
  • [PATCH 2/2] t1400: use show-ref to check pseudorefs, Phillip Wood via GitGitGadget
• GitGui tool - new local clone is missing commit(s) and missing a tag on master branch, Allan Ford
  • Re: GitGui tool - new local clone is missing commit(s) and missing a tag on master branch, Mark Levedahl
• What's cooking in git.git (Feb 2024, #03; Tue, 6), Junio C Hamano
  • Re: What's cooking in git.git (Feb 2024, #03; Tue, 6), Kousik Sanagavarapu
• [PATCH] restore: allow --staged on unborn branch, Ghanshyam Thakkar
  • Re: [PATCH] restore: allow --staged on unborn branch, Junio C Hamano
    • Re: [PATCH] restore: allow --staged on unborn branch, Ghanshyam Thakkar
• Query about gitignore, Divyaditya Singh
  • Re: Query about gitignore, Patrick Steinhardt
    • Message not available
      • Message not available
        • Re: Query about gitignore, Patrick Steinhardt
• Wrong exit code on failed SSH signing, Sergey Kosukhin
  • Re: Wrong exit code on failed SSH signing, Junio C Hamano
• Bug: git submodule update doesn't give a prompt to add pubkey of remote repo host, and failed because of it., DingJunyao
• gitk view could use a checkbox for stash, Britton Kerin
• gitk view Branches & tags field would benefit from globs, Britton Kerin
• is it a bug that git status show the in-progress 'edit' in an interactive rebase as 'done'?, Britton Kerin
  • Re: is it a bug that git status show the in-progress 'edit' in an interactive rebase as 'done'?, Oswald Buddenhagen
    • Re: is it a bug that git status show the in-progress 'edit' in an interactive rebase as 'done'?, Sergey Organov
    • Re: is it a bug that git status show the in-progress 'edit' in an interactive rebase as 'done'?, Britton Kerin
• [PATCH 0/4] merge-tree: handle missing objects correctly, Johannes Schindelin via GitGitGadget
  • [PATCH 2/4] merge-ort: do check `parse_tree()`'s return value, Johannes Schindelin via GitGitGadget
  • [PATCH 1/4] merge-tree: fail with a non-zero exit code on missing tree objects, Johannes Schindelin via GitGitGadget
    • Re: [PATCH 1/4] merge-tree: fail with a non-zero exit code on missing tree objects, Patrick Steinhardt
  • [PATCH 4/4] Always check `parse_tree*()`'s return value, Johannes Schindelin via GitGitGadget
    • Re: [PATCH 4/4] Always check `parse_tree*()`'s return value, Junio C Hamano
    • Re: [PATCH 4/4] Always check `parse_tree*()`'s return value, Patrick Steinhardt
  • [PATCH 3/4] t4301: verify that merge-tree fails on missing blob objects, Johannes Schindelin via GitGitGadget
  • Re: [PATCH 0/4] merge-tree: handle missing objects correctly, Junio C Hamano
  • Re: [PATCH 0/4] merge-tree: handle missing objects correctly, Patrick Steinhardt
  • [PATCH v2 0/5] merge-tree: handle missing objects correctly, Johannes Schindelin via GitGitGadget
    • [PATCH v2 1/5] merge-tree: fail with a non-zero exit code on missing tree objects, Johannes Schindelin via GitGitGadget
      • Re: [PATCH v2 1/5] merge-tree: fail with a non-zero exit code on missing tree objects, Eric Sunshine
        • Re: [PATCH v2 1/5] merge-tree: fail with a non-zero exit code on missing tree objects, Johannes Schindelin
    • [PATCH v2 2/5] merge-ort: do check `parse_tree()`'s return value, Johannes Schindelin via GitGitGadget
    • [PATCH v2 3/5] t4301: verify that merge-tree fails on missing blob objects, Johannes Schindelin via GitGitGadget
      • Re: [PATCH v2 3/5] t4301: verify that merge-tree fails on missing blob objects, Eric Sunshine
        • Re: [PATCH v2 3/5] t4301: verify that merge-tree fails on missing blob objects, Junio C Hamano
        • Re: [PATCH v2 3/5] t4301: verify that merge-tree fails on missing blob objects, Eric Sunshine
        • Re: [PATCH v2 3/5] t4301: verify that merge-tree fails on missing blob objects, Johannes Schindelin
    • [PATCH v2 4/5] Always check `parse_tree*()`'s return value, Johannes Schindelin via GitGitGadget
      • Re: [PATCH v2 4/5] Always check `parse_tree*()`'s return value, Eric Sunshine
        • Re: [PATCH v2 4/5] Always check `parse_tree*()`'s return value, Johannes Schindelin
          • Re: [PATCH v2 4/5] Always check `parse_tree*()`'s return value, Junio C Hamano
    • [PATCH v2 5/5] cache-tree: avoid an unnecessary check, Johannes Schindelin via GitGitGadget
      • Re: [PATCH v2 5/5] cache-tree: avoid an unnecessary check, Junio C Hamano
    • [PATCH v3 0/5] merge-tree: handle missing objects correctly, Johannes Schindelin via GitGitGadget
      • [PATCH v3 1/5] merge-tree: fail with a non-zero exit code on missing tree objects, Johannes Schindelin via GitGitGadget
        • Re: [PATCH v3 1/5] merge-tree: fail with a non-zero exit code on missing tree objects, Junio C Hamano
      • [PATCH v3 2/5] merge-ort: do check `parse_tree()`'s return value, Johannes Schindelin via GitGitGadget
        • Re: [PATCH v3 2/5] merge-ort: do check `parse_tree()`'s return value, Junio C Hamano
      • [PATCH v3 3/5] t4301: verify that merge-tree fails on missing blob objects, Johannes Schindelin via GitGitGadget
        • Re: [PATCH v3 3/5] t4301: verify that merge-tree fails on missing blob objects, Junio C Hamano
          • Re: [PATCH v3 3/5] t4301: verify that merge-tree fails on missing blob objects, Junio C Hamano
      • [PATCH v3 4/5] Always check `parse_tree*()`'s return value, Johannes Schindelin via GitGitGadget
        • Re: [PATCH v3 4/5] Always check `parse_tree*()`'s return value, Junio C Hamano
          • Re: [PATCH v3 4/5] Always check `parse_tree*()`'s return value, Johannes Schindelin
            • Re: [PATCH v3 4/5] Always check `parse_tree*()`'s return value, Junio C Hamano
      • [PATCH v3 5/5] cache-tree: avoid an unnecessary check, Johannes Schindelin via GitGitGadget
        • Re: [PATCH v3 5/5] cache-tree: avoid an unnecessary check, Junio C Hamano
      • [PATCH v4 0/6] merge-tree: handle missing objects correctly, Johannes Schindelin via GitGitGadget
        • [PATCH v4 1/6] merge-tree: fail with a non-zero exit code on missing tree objects, Johannes Schindelin via GitGitGadget
        • [PATCH v4 2/6] merge-ort: do check `parse_tree()`'s return value, Johannes Schindelin via GitGitGadget
        • [PATCH v4 3/6] t4301: verify that merge-tree fails on missing blob objects, Johannes Schindelin via GitGitGadget
        • [PATCH v4 5/6] cache-tree: avoid an unnecessary check, Johannes Schindelin via GitGitGadget
        • [PATCH v4 6/6] fill_tree_descriptor(): mark error message for translation, Johannes Schindelin via GitGitGadget
        • [PATCH v4 4/6] Always check `parse_tree*()`'s return value, Johannes Schindelin via GitGitGadget
        • Re: [PATCH v4 0/6] merge-tree: handle missing objects correctly, Junio C Hamano
• [PATCH] doc: diff-options: clarify --relative option, Han Young
• [PATCH 0/4] Speed up git-notes show, Maarten Bosmans
  • [PATCH 1/4] notes: print note blob to stdout directly, Maarten Bosmans
    • Re: [PATCH 1/4] notes: print note blob to stdout directly, Junio C Hamano
      • Re: [PATCH 1/4] notes: print note blob to stdout directly, Maarten Bosmans
        • Re: [PATCH 1/4] notes: print note blob to stdout directly, Junio C Hamano
          • Re: [PATCH 1/4] notes: print note blob to stdout directly, Jeff King
            • Re: [PATCH 1/4] notes: print note blob to stdout directly, Junio C Hamano
              • Re: [PATCH 1/4] notes: print note blob to stdout directly, Jeff King
                • Re: [PATCH 1/4] notes: print note blob to stdout directly, Junio C Hamano
                  • Re: [PATCH 1/4] notes: print note blob to stdout directly, Jeff King
                    • Re: [PATCH 1/4] notes: print note blob to stdout directly, Junio C Hamano
                      • Re: [PATCH 1/4] notes: print note blob to stdout directly, Jeff King
            • Re: [PATCH 1/4] notes: print note blob to stdout directly, Maarten Bosmans
              • Re: [PATCH 1/4] notes: print note blob to stdout directly, Jeff King
                • Re: [PATCH 1/4] notes: print note blob to stdout directly, Maarten Bosmans
                  • Re: [PATCH 1/4] notes: print note blob to stdout directly, Jeff King
          • Re: [PATCH 1/4] notes: print note blob to stdout directly, Maarten Bosmans
      • Re: [PATCH 1/4] notes: print note blob to stdout directly, Kristoffer Haugsbakk
  • [PATCH 2/4] notes: use exisisting function stream_blob_to_fd, Maarten Bosmans
    • Re: [PATCH 2/4] notes: use exisisting function stream_blob_to_fd, Eric Sunshine
  • [PATCH 3/4] notes: do not clean up right before calling die(), Maarten Bosmans
  • [PATCH 4/4] notes: use strbuf_attach to take ownership of the object contents, Maarten Bosmans
  • Re: [PATCH 0/4] Speed up git-notes show, Kristoffer Haugsbakk
    • Re: [PATCH 0/4] Speed up git-notes show, Maarten Bosmans
  • [PATCH v2 0/5] Speed up git-notes show, Maarten Bosmans
    • [PATCH v2 1/5] log: Move show_blob_object() to log.c, Maarten Bosmans
      • Re: [PATCH v2 1/5] log: Move show_blob_object() to log.c, Junio C Hamano
        • Re: [PATCH v2 1/5] log: Move show_blob_object() to log.c, Jeff King
          • Re: [PATCH v2 1/5] log: Move show_blob_object() to log.c, Junio C Hamano
          • Re: [PATCH v2 1/5] log: Move show_blob_object() to log.c, Maarten Bosmans
    • [PATCH v2 3/5] notes: use existing function stream_blob_to_fd, Maarten Bosmans
    • [PATCH v2 2/5] notes: avoid launching a child process to show a note blob, Maarten Bosmans
    • [PATCH v2 4/5] notes: do not clean up right before calling die(), Maarten Bosmans
    • [PATCH v2 5/5] notes: use strbuf_attach to take ownership of the object contents, Maarten Bosmans
      • Re: [PATCH v2 5/5] notes: use strbuf_attach to take ownership of the object contents, Jeff King
        • Re: [PATCH v2 5/5] notes: use strbuf_attach to take ownership of the object contents, Maarten Bosmans
• git-gui desktop launcher, Tobias Boesch
  • Re: git-gui desktop launcher, brian m. carlson
    • Re: git-gui desktop launcher, Junio C Hamano
      • Re: git-gui desktop launcher, Dragan Simic
        • Re: git-gui desktop launcher, Tobias Boesch
          • Re: git-gui desktop launcher, Dragan Simic
    • Re: git-gui desktop launcher, Tobias Boesch
      • Re: git-gui desktop launcher, brian m. carlson
  • Re: git-gui desktop launcher, Johannes Sixt
    • Re: git-gui desktop launcher, Marc Branchaud
    • Re: git-gui desktop launcher, Tobias Boesch
• Project Estimates, arnoldroberts123
  • <Possible follow-ups>
  • Project Estimates, krisbrannon920
• [PATCH] commit.c: ensure strchrnul() doesn't scan beyond range, Chandra Pratap via GitGitGadget
  • Re: [PATCH] commit.c: ensure strchrnul() doesn't scan beyond range, René Scharfe
    • Re: [PATCH] commit.c: ensure strchrnul() doesn't scan beyond range, Junio C Hamano
    • Re: [PATCH] commit.c: ensure strchrnul() doesn't scan beyond range, Jeff King
      • Re: [PATCH] commit.c: ensure strchrnul() doesn't scan beyond range, René Scharfe
        • Re: [PATCH] commit.c: ensure strchrnul() doesn't scan beyond range, Junio C Hamano
          • Re: [PATCH] commit.c: ensure strchrnul() doesn't scan beyond range, Kyle Lippincott
          • Re: [PATCH] commit.c: ensure strchrnul() doesn't scan beyond range, Jeff King
            • Re: [PATCH] commit.c: ensure strchrnul() doesn't scan beyond range, Junio C Hamano
  • Re: [PATCH] commit.c: ensure strchrnul() doesn't scan beyond range, Kyle Lippincott
  • [PATCH v2] commit.c: ensure find_header_mem() doesn't scan beyond given range, Chandra Pratap via GitGitGadget
    • Re: [PATCH v2] commit.c: ensure find_header_mem() doesn't scan beyond given range, René Scharfe
      • Re: [PATCH v2] commit.c: ensure find_header_mem() doesn't scan beyond given range, Junio C Hamano
• [Outreachy][PATCH 1/2] date: refactor 64 bit prereq code into reusable functions, Achu Luma
  • [Outreachy][PATCH 2/2] Port helper/test-date.c to unit-tests/t-date.c, Achu Luma
    • Re: [Outreachy][PATCH 2/2] Port helper/test-date.c to unit-tests/t-date.c, Ghanshyam Thakkar
      • Re: [Outreachy][PATCH 2/2] Port helper/test-date.c to unit-tests/t-date.c, Junio C Hamano
        • Re: [Outreachy][PATCH 2/2] Port helper/test-date.c to unit-tests/t-date.c, Patrick Steinhardt
          • Re: [Outreachy][PATCH 2/2] Port helper/test-date.c to unit-tests/t-date.c, Junio C Hamano
            • Re: [Outreachy][PATCH 2/2] Port helper/test-date.c to unit-tests/t-date.c, Patrick Steinhardt
              • Re: [Outreachy][PATCH 2/2] Port helper/test-date.c to unit-tests/t-date.c, Johannes Schindelin
  • RE: [Outreachy][PATCH 1/2] date: refactor 64 bit prereq code into reusable functions, rsbecker
    • Re: [Outreachy][PATCH 1/2] date: refactor 64 bit prereq code into reusable functions, Christian Couder
• [PATCH] Always check the return value of `repo_read_object_file()`, Johannes Schindelin via GitGitGadget
  • Re: [PATCH] Always check the return value of `repo_read_object_file()`, Karthik Nayak
    • Re: [PATCH] Always check the return value of `repo_read_object_file()`, Junio C Hamano
    • Re: [PATCH] Always check the return value of `repo_read_object_file()`, Johannes Schindelin
  • Re: [PATCH] Always check the return value of `repo_read_object_file()`, Kyle Lippincott
    • Re: [PATCH] Always check the return value of `repo_read_object_file()`, Johannes Schindelin
      • Re: [PATCH] Always check the return value of `repo_read_object_file()`, Junio C Hamano
      • Re: [PATCH] Always check the return value of `repo_read_object_file()`, Kyle Lippincott
  • Re: [PATCH] Always check the return value of `repo_read_object_file()`, Patrick Steinhardt
    • Re: [PATCH] Always check the return value of `repo_read_object_file()`, Junio C Hamano
    • Re: [PATCH] Always check the return value of `repo_read_object_file()`, Johannes Schindelin
      • Re: [PATCH] Always check the return value of `repo_read_object_file()`, Patrick Steinhardt
  • Re: [PATCH] Always check the return value of `repo_read_object_file()`, Junio C Hamano
    • Re: [PATCH] Always check the return value of `repo_read_object_file()`, Johannes Schindelin
  • [PATCH] Always check the return value of `repo_read_object_file()`, Teng Long
    • Re: [PATCH] Always check the return value of `repo_read_object_file()`, Johannes Schindelin
• [PATCH] branch: clarify <oldbranch> and <newbranch> terms further, Dragan Simic
  • Re: [PATCH] branch: clarify <oldbranch> and <newbranch> terms further, Kyle Lippincott
    • Re: [PATCH] branch: clarify <oldbranch> and <newbranch> terms further, Junio C Hamano
      • Re: [PATCH] branch: clarify <oldbranch> and <newbranch> terms further, Dragan Simic
        • Re: [PATCH] branch: clarify <oldbranch> and <newbranch> terms further, Junio C Hamano
          • Re: [PATCH] branch: clarify <oldbranch> and <newbranch> terms further, Dragan Simic
    • Re: [PATCH] branch: clarify <oldbranch> and <newbranch> terms further, Dragan Simic
• submodules: multiple alternative relative URL schemes?, Matthew Ogilvie
• [PATCH 0/2] Fix gitlab's token-based authentication w/ kerberos, Quentin Bouget
  • [PATCH 1/2] http: only reject basic auth credentials once they have been tried, Quentin Bouget
    • Re: [PATCH 1/2] http: only reject basic auth credentials once they have been tried, Junio C Hamano
      • Re: [PATCH 1/2] http: only reject basic auth credentials once they have been tried, Quentin Bouget
    • Re: [PATCH 1/2] http: only reject basic auth credentials once they have been tried, Patrick Steinhardt
  • [PATCH 2/2] http: prevent redirect from dropping credentials during reauth, Quentin Bouget
    • Re: [PATCH 2/2] http: prevent redirect from dropping credentials during reauth, brian m. carlson
      • Re: [PATCH 2/2] http: prevent redirect from dropping credentials during reauth, Quentin Bouget
        • Re: [PATCH 2/2] http: prevent redirect from dropping credentials during reauth, brian m. carlson
          • RE: [PATCH 2/2] http: prevent redirect from dropping credentials during reauth, rsbecker
    • Re: [PATCH 2/2] http: prevent redirect from dropping credentials during reauth, Junio C Hamano
      • Re: [PATCH 2/2] http: prevent redirect from dropping credentials during reauth, Quentin Bouget
    • RE: [PATCH 2/2] http: prevent redirect from dropping credentials during reauth, rsbecker
      • Re: [PATCH 2/2] http: prevent redirect from dropping credentials during reauth, Quentin Bouget
        • Re: [PATCH 2/2] http: prevent redirect from dropping credentials during reauth, Robert Coup
• [PATCH] .github/PULL_REQUEST_TEMPLATE.md: add a note about single-commit PRs, Philippe Blain via GitGitGadget
  • Re: [PATCH] .github/PULL_REQUEST_TEMPLATE.md: add a note about single-commit PRs, Junio C Hamano
    • Re: [PATCH] .github/PULL_REQUEST_TEMPLATE.md: add a note about single-commit PRs, Philippe Blain
      • Re: [PATCH] .github/PULL_REQUEST_TEMPLATE.md: add a note about single-commit PRs, Junio C Hamano
  • [PATCH v2] .github/PULL_REQUEST_TEMPLATE.md: add a note about single-commit PRs, Philippe Blain via GitGitGadget
• cpkotsoomcsin, IPHONE
• git-users: email list has become spam-drowned, Kristoffer Haugsbakk
  • Re: git-users: email list has become spam-drowned, Thomas Guyot
  • Re: git-users: email list has become spam-drowned, Junio C Hamano
    • Re: git-users: email list has become spam-drowned, Kristoffer Haugsbakk
  • Re: git-users: email list has become spam-drowned, Konstantin Khomoutov
  • Re: git-users: email list has become spam-drowned, Konstantin Khomoutov
    • Re: git-users: email list has become spam-drowned, Kristoffer Haugsbakk
• No one is aloud to make changes to dependency’s beside me- owner of domain and software!, ross nicholas Oneil thomas
• What's cooking in git.git (Feb 2024, #02; Fri, 2), Junio C Hamano
  • Re: What's cooking in git.git (Feb 2024, #02; Fri, 2), Phillip Wood
    • Re: What's cooking in git.git (Feb 2024, #02; Fri, 2), Junio C Hamano
      • Re: What's cooking in git.git (Feb 2024, #02; Fri, 2), Phillip Wood
  • Re: What's cooking in git.git (Feb 2024, #02; Fri, 2), Taylor Blau
• What's cooking in git.git (Feb 2024, #01; Fri, 2), Junio C Hamano
  • Re: What's cooking in git.git (Feb 2024, #01; Fri, 2), Junio C Hamano
• [PATCH 0/2] GitHub Actions update, Junio C Hamano
  • [PATCH 1/2] GitHub Actions: update to checkout@v4, Junio C Hamano
    • Message not available
      • Re: [PATCH 1/2] GitHub Actions: update to checkout@v4, Óscar Domínguez Celada
        • Re: [PATCH 1/2] GitHub Actions: update to checkout@v4, Junio C Hamano
  • [PATCH 2/2] GitHub Actions: update to github-script@v7, Junio C Hamano
• Hello question on Git for Windows 2.43.0 - GUID and/or SWID tag for this title, Christian Castro
  • Re: Hello question on Git for Windows 2.43.0 - GUID and/or SWID tag for this title, Kristoffer Haugsbakk
  • Re: Hello question on Git for Windows 2.43.0 - GUID and/or SWID tag for this title, Matthias Aßhauer
    • RE: Hello question on Git for Windows 2.43.0 - GUID and/or SWID tag for this title, Christian Castro
      • Re: Hello question on Git for Windows 2.43.0 - GUID and/or SWID tag for this title, Konstantin Khomoutov
        • Re: Hello question on Git for Windows 2.43.0 - GUID and/or SWID tag for this title, Konstantin Khomoutov
        • Re: Hello question on Git for Windows 2.43.0 - GUID and/or SWID tag for this title, Johannes Schindelin
          • Re: Hello question on Git for Windows 2.43.0 - GUID and/or SWID tag for this title, Kristoffer Haugsbakk
• [PATCH] sparse-index: pass string length to index_file_exists(), Jeff Hostetler via GitGitGadget
  • Re: [PATCH] sparse-index: pass string length to index_file_exists(), Junio C Hamano
    • Re: [PATCH] sparse-index: pass string length to index_file_exists(), Jeff Hostetler
      • Re: [PATCH] sparse-index: pass string length to index_file_exists(), Junio C Hamano
• single-char options, Martin Guy
  • Re: single-char options, Kristoffer Haugsbakk
  • Re: single-char options, Sergey Organov
  • Re: single-char options, Oswald Buddenhagen
• Git submodule ssh command recursion bug, David Weber
• [PATCH] t/t3515-cherry-pick-rebase.sh: new testcase demonstrating broken behavior, Vegard Nossum
  • Re: [PATCH] t/t3515-cherry-pick-rebase.sh: new testcase demonstrating broken behavior, Phillip Wood
    • [PATCH 2/2] sequencer: unset GIT_CHERRY_PICK_HELP for 'exec' commands, Vegard Nossum
      • Re: [PATCH 2/2] sequencer: unset GIT_CHERRY_PICK_HELP for 'exec' commands, Kristoffer Haugsbakk
        • Re: [PATCH 2/2] sequencer: unset GIT_CHERRY_PICK_HELP for 'exec' commands, Junio C Hamano
          • Re: [PATCH 2/2] sequencer: unset GIT_CHERRY_PICK_HELP for 'exec' commands, Vegard Nossum
            • Re: [PATCH 2/2] sequencer: unset GIT_CHERRY_PICK_HELP for 'exec' commands, Junio C Hamano
              • Re: [PATCH 2/2] sequencer: unset GIT_CHERRY_PICK_HELP for 'exec' commands, Phillip Wood
                • Re: [PATCH 2/2] sequencer: unset GIT_CHERRY_PICK_HELP for 'exec' commands, Junio C Hamano
                  • Re: [PATCH 2/2] sequencer: unset GIT_CHERRY_PICK_HELP for 'exec' commands, Vegard Nossum
                    • Re: [PATCH 2/2] sequencer: unset GIT_CHERRY_PICK_HELP for 'exec' commands, Phillip Wood
                      • Re: [PATCH 2/2] sequencer: unset GIT_CHERRY_PICK_HELP for 'exec' commands, Junio C Hamano
                        • Re: [PATCH 2/2] sequencer: unset GIT_CHERRY_PICK_HELP for 'exec' commands, Phillip Wood
                          • Re: [PATCH 2/2] sequencer: unset GIT_CHERRY_PICK_HELP for 'exec' commands, Junio C Hamano
                            • Re: [PATCH 2/2] sequencer: unset GIT_CHERRY_PICK_HELP for 'exec' commands, Vegard Nossum
                              • Re: [PATCH 2/2] sequencer: unset GIT_CHERRY_PICK_HELP for 'exec' commands, Junio C Hamano
• [PATCH] imap-send: add missing "strbuf.h" include under NO_CURL, Philippe Blain via GitGitGadget
  • Re: [PATCH] imap-send: add missing "strbuf.h" include under NO_CURL, Elijah Newren
• [ANNOUNCE] Git Rev News edition 107, Christian Couder
• Migrate away from vger to GitHub or (on-premise) GitLab?, Hans Meiser
  • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Kristoffer Haugsbakk
    • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Hans Meiser
  • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Antonin Delpeuch
  • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Dragan Simic
  • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Konstantin Ryabitsev
    • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Dragan Simic
      • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Dragan Simic
    • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Hans Meiser
      • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Dragan Simic
        • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Hans Meiser
          • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Dragan Simic
            • RE: Migrate away from vger to GitHub or (on-premise) GitLab?, rsbecker
              • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Dragan Simic
              • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Hans Meiser
            • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Hans Meiser
              • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Dragan Simic
                • Muting and unmuting threads (Was: Migrate away from vger to GitHub or (on-premise) GitLab?), Dragan Simic
            • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Phillip Wood
              • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Dragan Simic
              • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Junio C Hamano
          • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, brian m. carlson
            • Re: Migrate away from vger to GitHub or (on-premise) GitLab?, Patrick Steinhardt