Harald Nordgren
@HaraldNordgren on GitHub. Posts as haraldnordgren@gmail.com.
963
messages
659
patches posted
63%
of 24 series merged
42
threads started
2018
first message, Apr 2, 2018
34 hours
since the latest message
Patch series
Of 37 patch series (re-rolls counted once), 15 landed on master and 9 did not; 13 posted in the last 90 days are still in review.
- in reviewstatus, push: handle a push branch rebased onto a newer upstreamOct 6, 2026
- in reviewci: link failure and leak annotations to the test scriptv6, Oct 6, 2026
- in reviewbranch: let --delete-merged default to every upstreamv2, Oct 4, 2026
- in reviewfetch: avoid fetching every branch of a new remote in a shallow repov6, Oct 4, 2026
- in reviewobject-name: accept @{p} as short for @{push}v2, Oct 2, 2026
- in reviewremote: allow a list of remotes in remote.pushDefaultOct 2, 2026
- in reviewstash: allow custom conflict labels for popSep 30, 2026
- in reviewbranch: let --delete-merged find squash merged branchesSep 29, 2026
- in reviewobject-name: explain why <ref>~N fails in a shallow clonev3, Sep 23, 2026
- in reviewrange-diff: add --matched-only to skip one-sided commitsv3, Sep 15, 2026
- in reviewci: drop no-op gettext link on macOSv2, Sep 14, 2026
- in reviewci: only warn about perforce/git-lfs/JGit on platforms that need themSep 12, 2026
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
- push: suggest a force push after a clean rebase
- push: offer a force push after rewriting pushed commits
- push: name the branch to pull from when it is not the upstream
- status: suggest a force push after a clean rebase
- status: say when the push branch was rebased cleanly
- status: count push divergence outside the upstream
- status, push: handle a push branch rebased onto a newer upstream
- ci: point test failures and fixed known breakages at their file and line
- ci: annotate leaks and stop a leak-sanitizer script at its first failure
- ci: link failure and leak annotations to the test script
- Re: [PATCH v6 0/4] fetch: avoid fetching every branch of a new remote in a shallow repo
- Re: [PATCH v5 0/2] ci: link failure and leak annotations to the test script
- Re: [PATCH] branch: let --delete-merged find squash merged branches
- Re: [PATCH v6 0/4] fetch: avoid fetching every branch of a new remote in a shallow repo
- Re: [PATCH] branch: let --delete-merged default to every upstream
- Re: [PATCH] branch: let --delete-merged default to every upstream
- Re: [PATCH v5 0/2] ci: link failure and leak annotations to the test script
- Re: [PATCH v5 0/2] ci: link failure and leak annotations to the test script
- branch: let --delete-merged default to every upstream
- remote: default to --limited-fetch in a shallow repository
- remote: add "git remote add --limited-fetch"
- fetch: infer branches to fetch from a refmap-only remote
- fetch: add remote.<name>.refmap
- fetch: avoid fetching every branch of a new remote in a shallow repo
- ci: point test failures and fixed known breakages at their file and line
- ci: annotate leaks and stop a leak-sanitizer script at its first failure
- ci: link failure and leak annotations to the test script
- branch: let --delete-merged default to every upstream
- Re: [PATCH v2] object-name: accept @{p} as short for @{push}
- Re: [PATCH v4 2/2] ci: point test failures and fixed known breakages at their file and line