messages from 2025-09-16 20:16:01 to 2025-09-18 06:57:04 UTC [more...]
Fwd: Why does git-status suggest different commands to unstage files depending on whether there is a commit yet or not?
2025-09-18 6:56 UTC (3+ messages)
` "
[PATCH 0/5] builtin/config: bug fixes for "get" subcommand with "--type=color"
2025-09-18 6:49 UTC (8+ messages)
` [PATCH v3 "
` [PATCH v3 1/5] t1300: write test expectations in the test's body
` [PATCH v3 2/5] t1300: small style fixups
` [PATCH v3 3/5] builtin/config: do not die in `get_color()`
` [PATCH v3 4/5] builtin/config: special-case retrieving colors without a key
` [PATCH v3 5/5] builtin/config: do not spawn pager when printing color codes
[PATCH] mailmap: consolidate multiple addresses into one
2025-09-18 6:41 UTC (5+ messages)
[Change] Git build issue on NonStop
2025-09-18 6:31 UTC (5+ messages)
[PATCH v2 0/5] builtin/config: bug fixes for "get" subcommand with "--type=color"
2025-09-18 6:03 UTC (4+ messages)
` [PATCH v2 5/5] builtin/config: do not spawn pager when printing color codes
What's cooking in git.git (Sep 2025, #06; Mon, 15)
2025-09-18 5:52 UTC (7+ messages)
[PATCH v2] combine-diff: don't override recursive flag in diff_tree_combined()
2025-09-18 5:49 UTC (4+ messages)
[GSoC][PATCH v2 0/5] Add refs optimize subcommand
2025-09-18 5:47 UTC (11+ messages)
` [GSoC][PATCH v3 0/9] "
` [GSoC][PATCH v3 1/9] refs: add a generic 'optimize' API
` [GSoC][PATCH v3 2/9] files-backend: implement 'optimize' action
` [GSoC][PATCH v3 3/9] reftable-backend: "
` [GSoC][PATCH v3 4/9] builtin/pack-refs: convert to use the generic refs_optimize() API
` [GSoC][PATCH v3 5/9] builtin/pack-refs: factor out core logic into a shared library
` [GSoC][GSoC][PATCH v3 6/9] doc: pack-refs: factor out common options
` [GSoC][PATCH v3 7/9] builtin/refs: add optimize subcommand
` [GSoC][PATCH v3 8/9] t0601: refactor tests to be shareable
` [GSoC][PATCH v3 9/9] t: add test for git refs optimize subcommand
I still use it
2025-09-18 5:37 UTC (2+ messages)
[PATCH RFC 0/3] Introduce Rust and announce that it will become mandatorty
2025-09-18 3:47 UTC (13+ messages)
` [PATCH v5 0/9] Introduce Rust and announce that it will become mandatory
` [PATCH v5 7/9] BreakingChanges: announce Rust becoming mandatory
[PATCH] Add `-u` short option for `git pull`
2025-09-18 0:32 UTC (4+ messages)
[PATCH 00/15] Introduce rust: In xdiff
2025-09-17 23:31 UTC (39+ messages)
` [PATCH v2 00/18] "
` [PATCH v2 01/18] cleanup: rename variables that collide with Rust primitive type names
` [PATCH v2 02/18] make: add -fPIE flag
` [PATCH v2 03/18] make: merge xdiff lib into libgit.a
` [PATCH v2 04/18] make: merge reftable "
` [PATCH v2 05/18] doc: add a policy for using Rust
` [PATCH v2 06/18] BreakingChanges: announce Rust becoming mandatory
` [PATCH v2 07/18] build: introduce rust
` [PATCH v2 08/18] help: report on whether or not Rust is enabled
` [PATCH v2 09/18] github workflows: install rust
` [PATCH v2 10/18] win+Meson: do allow linking with the Rust-built xdiff
` [PATCH v2 11/18] github workflows: upload Cargo.lock
` [PATCH v2 12/18] build: new crate, build-helper
` [PATCH v2 13/18] build-helper: link against libgit.a and any other required C libraries
` [PATCH v2 14/18] build-helper: cbindgen, let crates generate a header file
` [PATCH v2 15/18] varint: use explicit width for integers
` [PATCH v2 16/18] build: new crate, misc
` [PATCH v2 17/18] misc: use BuildHelper
` [PATCH v2 18/18] misc::varint: reimplement as test balloon for Rust
[Bug] git fetch --dry-run --filter makes changes to .git/config
2025-09-17 23:23 UTC (3+ messages)
[PATCH 0/2] doc: git-push: clarify section
2025-09-17 22:35 UTC (4+ messages)
` [PATCH 1/2] doc: git-push: create PUSH RULES section
` [PATCH 2/2] doc: git-push: rewrite refspec specification
[PATCH v5 00/15] packfile: carve out a new packfile store
2025-09-17 22:32 UTC (9+ messages)
` [PATCH v5 01/15] packfile: introduce a new `struct packfile_store`
` [PATCH v5 04/15] odb: move packfile map into "
` [PATCH v5 05/15] odb: move MRU list of packfiles "
` [PATCH v5 09/15] packfile: split up responsibilities of `reprepare_packed_git()`
[PATCH 0/2] refs/files: fix issues with git-fetch on case-insensitive FS
2025-09-17 20:40 UTC (32+ messages)
` [PATCH v3 0/4] "
` [PATCH v3 1/4] refs/files: catch conflicts on case-insensitive file-systems
` [PATCH v3 2/4] refs/files: use correct error type when lock exists
` [PATCH v3 3/4] refs/files: handle F/D conflicts in case-insensitive FS
` [PATCH v4 0/4] refs/files: fix issues with git-fetch on "
` [PATCH v4 1/4] refs/files: catch conflicts on case-insensitive file-systems
` [PATCH v4 2/4] refs/files: use correct error type when lock exists
` [PATCH v4 3/4] refs/files: handle F/D conflicts in case-insensitive FS
` [PATCH v4 4/4] refs/files: handle D/F conflicts during locking
[PATCH v4 0/7] you-still-use-that??: improve breaking changes troubleshooting
2025-09-17 20:24 UTC (17+ messages)
` [PATCH v5 0/8] "
` [PATCH v6 0/9] "
` [PATCH v6 1/9] Makefile: don’t add whatchanged after it has been removed
` [PATCH v6 2/9] git: add `deprecated` category to --list-cmds
` [PATCH v6 3/9] git: move seen-alias bookkeeping into handle_alias(...)
` [PATCH v6 4/9] git: allow alias-shadowing deprecated builtins
` [PATCH v6 5/9] t0014: test shadowing of aliases for a sample of builtins
` [PATCH v6 6/9] you-still-use-that??: help the user help themselves
` [PATCH v6 7/9] whatchanged: hint about git-log(1) and aliasing
` [PATCH v6 8/9] whatchanged: remove not-even-shorter clause
` [PATCH v6 9/9] BreakingChanges: remove claim about whatchanged reports
safe.directory does not work at all (git 2.39.5, 2.51.0)
2025-09-17 20:22 UTC (5+ messages)
` [SOLVED] "
[PATCH RFC 00/11] Introduce git-history(1) command for easy history editing
2025-09-17 20:12 UTC (4+ messages)
What's cooking in git.git (Sep 2025, #07; Wed, 17)
2025-09-17 18:52 UTC
[PATCH 0/4] doc: git-push: clarify DESCRIPTION section & refspec definition
2025-09-17 18:42 UTC (7+ messages)
` [PATCH v2 "
` [PATCH v2 1/4] doc: git-push: clarify intro
[PATCH v3 0/6] doc: git-checkout: clarify DESCRIPTION section
2025-09-17 18:38 UTC (3+ messages)
` [PATCH v4 0/7] "
[PATCH 0/2] fast-import: start controlling how commit signatures are handled
2025-09-17 18:27 UTC (8+ messages)
` [PATCH 2/2] fast-import: add '--signed-commits=<mode>' option
[PATCH v2 0/2] fast-import: start controlling how commit signatures are handled
2025-09-17 18:23 UTC (9+ messages)
` [PATCH v2 2/2] fast-import: add '--signed-commits=<mode>' option
` [PATCH v3 0/2] fast-import: start controlling how commit signatures are handled
` [PATCH v3 1/2] gpg-interface: refactor 'enum sign_mode' parsing
` [PATCH v3 2/2] fast-import: add '--signed-commits=<mode>' option
[PATCH 0/6] breaking changes: switch default initial branch name to "main"
2025-09-17 16:18 UTC (10+ messages)
` [PATCH v3 0/4] "
` [PATCH v2 5/4] initial branch: give hints after switching the default name
Why does git-status suggest different commands to unstage files depending on whether there is a commit yet or not?
2025-09-17 15:33 UTC (6+ messages)
[PATCH 0/3] extend --ignore-other-worktrees to 'rebase', add hints
2025-09-17 15:25 UTC (8+ messages)
` [PATCH 1/3] checkout: provide hint when failing due to another worktree
[PATCH 0/2] Make git-clone(1) more resilient when using bundle-URI
2025-09-17 14:30 UTC (5+ messages)
` [PATCH 2/2] bundle-uri: do not abort on invalid packet line
[PATCH] send-email: don't duplicate Reply-to: in intro message
2025-09-17 14:05 UTC (3+ messages)
[PATCH 00/17] Use rust types in xdiff
2025-09-17 13:53 UTC (6+ messages)
New September Order. 15372 Wednesday, September 17, 2025 at 11:57:41 AM
2025-09-17 9:57 UTC
[PATCH 0/4] enhance string-list API to fix sign compare warnings
2025-09-17 9:20 UTC (6+ messages)
` [PATCH v2 "
` [PATCH v2 1/4] string-list: use bool instead of int for "exact_match"
` [PATCH v2 2/4] string-list: replace negative index encoding with "exact_match" parameter
` [PATCH v2 3/4] string-list: change "string_list_find_insert_index" return type to "size_t"
` [PATCH v2 4/4] refs: enable sign compare warnings check
Participating in the Outreachy December 2025 cohort
2025-09-17 6:19 UTC (2+ messages)
[PATCH] send-email: don't duplicate Reply-to:
2025-09-17 6:21 UTC (3+ messages)
[PATCH] repo: add --all to git-repo-info
2025-09-17 5:34 UTC (4+ messages)
Bug or just a mistake : --shallow-exclude parameter behavior anomalies in Git 2.45.2: "no commits selected" and "ambiguous deepen-not" errors
2025-09-17 2:54 UTC (3+ messages)
` --shallow-exclude=ref -> "ambiguous deepen-not" error
[PATCH 0/13] unraveling the mysteries of color variables
2025-09-16 23:13 UTC (15+ messages)
` [PATCH 03/13] grep: don't treat grep_opt.color as a strict bool
` [PATCH 04/13] diff: simplify color_moved check when flushing
` [PATCH 05/13] diff: don't use diff_options.use_color as a strict bool
` [PATCH 06/13] diff: pass o->use_color directly to fill_metainfo()
` [PATCH 07/13] diff: stop passing ecbdata->use_color as boolean
` [PATCH 08/13] pretty: use format_commit_context.auto_color as colorbool
` [PATCH 09/13] color: use git_colorbool enum to type to store colorbools
` [PATCH v1.5 9/13] color: use git_colorbool enum "
` [PATCH 10/13] color: return bool from want_color()
` [PATCH 11/13] add-interactive: retain colorbool values longer
` [PATCH 12/13] config: store want_color() result in a separate bool
` [PATCH 13/13 DO NOT APPLY] color: convert git_colorbool into a struct
t5564 seems to be failing on Debian unstable
2025-09-16 22:46 UTC (2+ messages)
[RFC] git-rebase-clean: mitigating a “semantic conflict cascade” during rebase
2025-09-16 22:14 UTC (2+ messages)
[PATCH v2 1/4] doc: git-push: clarify intro
2025-09-16 21:59 UTC (3+ messages)
[ANNOUNCE] tig-2.5.12
2025-09-16 20:32 UTC (2+ messages)
` [ANNOUNCE] tig-2.6.0
--shallow-exclude=ref -> "ambiguous deepen-not" error
2025-09-16 20:34 UTC (2+ messages)
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
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 NNTP newsgroup(s).