git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
 messages from 2024-02-20 03:27:35 to 2024-02-22 15:52:58 UTC [more...]

Git in GSoC 2024
 2024-02-22 15:52 UTC  (19+ messages)

[PATCH 0/4] merge-tree: handle missing objects correctly
 2024-02-22 14:36 UTC  (17+ messages)
` [PATCH v2 0/5] "
  ` [PATCH v2 1/5] merge-tree: fail with a non-zero exit code on missing tree objects
  ` [PATCH v2 3/5] t4301: verify that merge-tree fails on missing blob objects
  ` [PATCH v2 4/5] Always check `parse_tree*()`'s return value
  ` [PATCH v3 0/5] merge-tree: handle missing objects correctly
    ` [PATCH v3 1/5] merge-tree: fail with a non-zero exit code on missing tree objects
    ` [PATCH v3 2/5] merge-ort: do check `parse_tree()`'s return value
    ` [PATCH v3 3/5] t4301: verify that merge-tree fails on missing blob objects
    ` [PATCH v3 4/5] Always check `parse_tree*()`'s return value
    ` [PATCH v3 5/5] cache-tree: avoid an unnecessary check

Hello question on Git for Windows 2.43.0 - GUID and/or SWID tag for this title
 2024-02-22 13:35 UTC  (6+ messages)

[PATCH 00/12] The merge-base logic vs missing commit objects
 2024-02-22 13:21 UTC  (13+ messages)
` [PATCH v2 00/11] "
  ` [PATCH v2 01/11] paint_down_to_common: plug two memory leaks
  ` [PATCH v2 02/11] Prepare `repo_in_merge_bases_many()` to optionally expect missing commits
  ` [PATCH v2 03/11] Start reporting missing commits in `repo_in_merge_bases_many()`
  ` [PATCH v2 04/11] Prepare `paint_down_to_common()` for handling shallow commits
  ` [PATCH v2 05/11] commit-reach: start reporting errors in `paint_down_to_common()`
  ` [PATCH v2 06/11] merge_bases_many(): pass on errors from `paint_down_to_common()`
  ` [PATCH v2 07/11] get_merge_bases_many_0(): pass on errors from `merge_bases_many()`
  ` [PATCH v2 08/11] repo_get_merge_bases(): "
  ` [PATCH v2 09/11] get_octopus_merge_bases(): "
  ` [PATCH v2 10/11] repo_get_merge_bases_many(): "
  ` [PATCH v2 11/11] repo_get_merge_bases_many_dirty(): "

[PATCH 0/5] for-each-ref: print all refs on empty string pattern
 2024-02-22 13:17 UTC  (6+ messages)
` [PATCH v4 0/5] for-each-ref: add '--include-root-refs' option
  ` [PATCH v4 5/5] for-each-ref: add new option to include root refs

[PATCH] rebase: make warning less passive aggressive
 2024-02-22 11:04 UTC  (16+ messages)
` [PATCH v2] "

[PATCH 0/3] Doc placeholders
 2024-02-22  9:07 UTC  (13+ messages)
` [PATCH 1/3] doc: git-rev-parse: enforce command-line description syntax
` [PATCH 2/3] doc: git-clone fix missing placeholder end carret
` [PATCH 3/3] doc: add some missing sentence dots

Segfault: git show-branch --reflog refs/pullreqs/1
 2024-02-22  9:02 UTC  (14+ messages)
` [PATCH 0/2] Detect empty or missing reflogs with `ref@{0}`
  ` [PATCH 1/2] object-name: detect and report empty reflogs
  ` [PATCH 2/2] builtin/show-branch: detect "

What's cooking in git.git (Feb 2024, #07; Tue, 20)
 2024-02-22  8:25 UTC  (4+ messages)

[PATCH] Add unix domain socket support to HTTP transport
 2024-02-22  3:04 UTC  (3+ messages)

[PATCH] builtin/stash: configs keepIndex, includeUntracked
 2024-02-21 23:53 UTC  (14+ messages)

script to pre-build all commits in a git-bisect, and use them during testing
 2024-02-21 23:20 UTC  (2+ messages)

[PATCH] doc: clarify the format of placeholders
 2024-02-21 21:18 UTC 

Bug: impure renames may be reported as pure renames
 2024-02-21 21:00 UTC  (4+ messages)

[PATCH] git-remote.txt: fix typo
 2024-02-21 18:18 UTC  (2+ messages)

[PATCH 0/4] completion for git-reflog show
 2024-02-21 18:06 UTC  (6+ messages)
` [PATCH 3/4] completion: reflog with implicit "show"

[PATCH 0/5] promise: introduce promises to track success or error
 2024-02-21 18:03 UTC  (7+ messages)

Breaking change with "git log -n" since 2.43
 2024-02-21 17:51 UTC  (10+ messages)

[PATCH 00/12] FSMonitor edge cases on case-insensitive file systems
 2024-02-21 12:54 UTC  (18+ messages)
` [PATCH 01/12] sparse-index: pass string length to index_file_exists()
` [PATCH 02/12] name-hash: add index_dir_exists2()
` [PATCH 04/12] fsmonitor: refactor refresh callback on directory events
` [PATCH 06/12] fsmonitor: clarify handling of directory events in callback

[PATCH 0/6] reflog: introduce subcommand to list reflogs
 2024-02-21 12:37 UTC  (35+ messages)
` [PATCH 2/6] dir-iterator: support iteration in sorted order
` [PATCH 3/6] refs/files: sort reflogs returned by the reflog iterator
` [PATCH 4/6] refs: drop unused params from the reflog iterator callback
` [PATCH 5/6] refs: stop resolving ref corresponding to reflogs
` [PATCH 6/6] builtin/reflog: introduce subcommand to list reflogs
` [PATCH v2 0/7] reflog: "
  ` [PATCH v2 1/7] dir-iterator: pass name to `prepare_next_entry_data()` directly
  ` [PATCH v2 2/7] dir-iterator: support iteration in sorted order
  ` [PATCH v2 3/7] refs/files: sort reflogs returned by the reflog iterator
  ` [PATCH v2 4/7] refs: always treat iterators as ordered
  ` [PATCH v2 5/7] refs: drop unused params from the reflog iterator callback
  ` [PATCH v2 6/7] refs: stop resolving ref corresponding to reflogs
  ` [PATCH v2 7/7] builtin/reflog: introduce subcommand to list reflogs
` [PATCH v3 0/8] reflog: "
  ` [PATCH v3 1/8] dir-iterator: pass name to `prepare_next_entry_data()` directly
  ` [PATCH v3 2/8] dir-iterator: support iteration in sorted order
  ` [PATCH v3 3/8] refs/files: sort reflogs returned by the reflog iterator
  ` [PATCH v3 4/8] refs/files: sort merged worktree and common reflogs
  ` [PATCH v3 5/8] refs: always treat iterators as ordered
  ` [PATCH v3 6/8] refs: drop unused params from the reflog iterator callback
  ` [PATCH v3 7/8] refs: stop resolving ref corresponding to reflogs
  ` [PATCH v3 8/8] builtin/reflog: introduce subcommand to list reflogs

[PATCH] documentation: send-email: use camel case consistently
 2024-02-21  7:50 UTC  (10+ messages)

[PATCH v4] mergetools: vimdiff: use correct tool's name when reading mergetool config
 2024-02-21  5:20 UTC  (2+ messages)

Git rebasing attribute the change to the wrong file [bug]
 2024-02-21  2:18 UTC  (2+ messages)

[PATCH 0/1] completion: send-email: don't complete revs when --no-format-patch
 2024-02-21  1:34 UTC  (5+ messages)
  ` [PATCH v2 1/1] completion: "

[PATCH v4] documentation: send-email: use camel case consistently
 2024-02-21  0:04 UTC  (3+ messages)

[PATCH v3] documentation: send-email: use camel case consistently
 2024-02-20 22:21 UTC  (5+ messages)

[PATCH] branch: rework the descriptions of rename and copy operations
 2024-02-20 20:34 UTC  (17+ messages)
                    ` [PATCH] branch: adjust documentation

[PATCH] Revert "Declare both git-switch and git-restore experimental"
 2024-02-20 19:57 UTC  (9+ messages)

[ANNOUNCE] Git for Windows 2.44.0-rc2
 2024-02-20 19:06 UTC 

[PATCH 00/12] reftable: improve ref iteration performance (pt.2)
 2024-02-20 18:25 UTC  (5+ messages)
` [PATCH 02/12] reftable/merged: make `merged_iter` structure private
` [PATCH 03/12] reftable/merged: advance subiter on subsequent iteration

[ANNOUNCE] Git v2.44.0-rc2
 2024-02-20 17:09 UTC 

[PATCH 0/4] Speed up git-notes show
 2024-02-20 11:40 UTC  (9+ messages)
` [PATCH v2 0/5] "
  ` [PATCH v2 1/5] log: Move show_blob_object() to log.c
  ` [PATCH v2 5/5] notes: use strbuf_attach to take ownership of the object contents

Git difftool: interaction between --dir-diff and --trust-exit-code
 2024-02-20 10:08 UTC  (5+ messages)
` [PATCH] git-difftool--helper: honor `--trust-exit-code` with `--dir-diff`
` [PATCH v2] "

[PATCH v2] documentation: send-email: use camel case consistently
 2024-02-20  7:04 UTC 

Why does the includeif woks how it does?
 2024-02-20  6:54 UTC 

[BUG] git commit --trailer --verbose puts trailer below scissors line
 2024-02-20  3:26 UTC  (6+ messages)
      ` [PATCH] trailer: fix comment/cut-line regression with opts->no_divider


Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).