Han Jiang

Patch series

Of 1 patch series (re-rolls counted once), 1 landed on master and 0 did not.

• mergeddoc: add missing commit C to the graph for --ancestry-path=H D..MMar 16, 2025, 5af21c9acb

A series is merged when one of its patches matches a commit on master by the same author, by subject. Versions are linked when they share a patch subject. Patches reworded before landing, or applied under someone else's name, count as not merged.

Recent emails

• Nov 30, 2025`git diff --max-depth` results in fatal error when comparing a merge commit with its parents
• Nov 29, 2025`--max-depth` produces no output when <path> is '.' or ends with slash
• Nov 20, 2025`git config get --type=path` results in segmentation fault on value starting with `:(optional)`
• Jul 24, 2025`git remote get-url --push`: `url.<base>.pushInsteadOf` is ignored (while `url.<base>.insteadOf` is not)
• Jul 24, 2025`git remote rename` does not work when `refs/remotes/server/HEAD` is unborn (when right after `git remote add -m`)
• Mar 16, 2025Re: [PATCH] doc: add missing commit C to the graph for --ancestry-path=H D..M
• Mar 16, 2025Re: `--ancestry-path` documentation has wrong graph
• Mar 16, 2025doc: add missing commit C to the graph for --ancestry-path=H D..M
• Mar 15, 2025Re: `--ancestry-path` documentation has wrong graph
• Mar 15, 2025Re: `--ancestry-path` documentation has wrong graph
• Mar 13, 2025`--word-diff` documentation formatting error
• Mar 13, 2025`--ancestry-path` documentation has wrong graph
• Sep 11, 2024Re: `git diff --break-rewrites` does not work (otherwise it should break rewrite into delete and create, for `--find-renames` to work)
• Sep 10, 2024`git diff --break-rewrites` does not work (otherwise it should break rewrite into delete and create, for `--find-renames` to work)
• Sep 10, 2024Re: `git remote set-branches (without --add) <name> <branch>… ` does not add refspecs to `remote.<remote>.fetch` when `remote.<remote>.fetch` does not exist
• Sep 5, 2024Re: `git remote set-branches (without --add) <name> <branch>… ` does not add refspecs to `remote.<remote>.fetch` when `remote.<remote>.fetch` does not exist
• Sep 5, 2024Re: `git log FETCH_HEAD` only logs whatever happens to be the first among the fetched refs (instead of all the fetched refs)
• Sep 5, 2024`git fetch <remote> <refspec>…` <refspec (without dst)>s are mapped by other <refspec (with dst)> resulting in extra remote tracking branches
• Sep 5, 2024`git log FETCH_HEAD` only logs whatever happens to be the first among the fetched refs (instead of all the fetched refs)
• Sep 4, 2024Re: `git fetch --refmap=<refspec>… <repository> <refspec>… ` providing NON-empty <refspec> to the --refmap ALSO causes Git to ignore the configured refspecs
• Sep 4, 2024Re: `git fetch --refmap=<refspec>… <repository> <refspec>…​` providing NON-empty <refspec> to the --refmap ALSO causes Git to ignore the configured refspecs
• Sep 4, 2024Re: `git fetch --refmap=<refspec>… <repository> <refspec>… ` providing NON-empty <refspec> to the --refmap ALSO causes Git to ignore the configured refspecs
• Sep 4, 2024Re: `git merge --no-overwrite-ignore` overwrites ignored files when merge (i.e. not fast-forward)
• Sep 4, 2024`git fetch --refmap=<refspec>… <repository> <refspec>…​` providing NON-empty <refspec> to the --refmap ALSO causes Git to ignore the configured refspecs
• Sep 4, 2024`git remote prune <remote>…​` (equivalent to git fetch --prune <remote> except that no new references will be fetched) ignores `fetch.pruneTags` (and `git fetch --dry-run` prints same tag twice)
• Sep 3, 2024`git remote show <name>…​` does not show all branches capable of `git push` when `push.default=upstream` and behaves as if `push.default=simple`
• Sep 3, 2024`git remote set-url <remote> <newurl> [<oldurl>]` fails to set first url when multiple urls are selected
• Sep 3, 2024`git remote set-branches (without --add) <name> <branch>…​` does not add refspecs to `remote.<remote>.fetch` when `remote.<remote>.fetch` does not exist
• Sep 1, 2024Re: `git rebase (--no-fork-point) --onto=<newbase> [<upstream> [<branch>]]` leaves HEAD detached and *HEAD not moved when <branch> is exactly `HEAD`
• Sep 1, 2024`git rebase (--no-fork-point) --onto=<newbase> [<upstream> [<branch>]]` leaves HEAD detached and *HEAD not moved when <branch> is exactly `HEAD`

Search their messages