Chris Down
@cdown on GitHub. Posts as chris@chrisdown.name.
20
messages
8
patches posted
33%
of 3 series merged
5
threads started
2014
first message, Dec 10, 2014
Jun 9, 2025
since the latest message
Patch series
Of 3 patch series (re-rolls counted once), 1 landed on master and 2 did not.
- not mergedcommit: Add commit.signoff configuration optionMay 13, 2025
- mergedbisect: status improvements when bisect is not fully fleshed outv3, May 11, 2022, 0cf1defa5a
- not mergedbisect--helper: warn if we are assuming an unlikely pathspecMay 1, 2022
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
- Re: [PATCH] commit: Add commit.signoff configuration option
- Re: [PATCH] commit: Add commit.signoff configuration option
- Re: [PATCH] commit: Add commit.signoff configuration option
- Re: [PATCH] commit: Add commit.signoff configuration option
- Re: [PATCH] commit: Add commit.signoff configuration option
- Re: [PATCH] commit: Add commit.signoff configuration option
- commit: Add commit.signoff configuration option
- bisect: output bisect setup status in bisect log
- bisect: output state before we are ready to compute bisection
- bisect: status improvements when bisect is not fully fleshed out
- Re: [PATCH v2 0/2] bisect: status improvements when bisect is not fully fleshed out
- Re: [PATCH v2 0/2] bisect: status improvements when bisect is not fully fleshed out
- Re: [PATCH v2 1/2] bisect: output state before we are ready to compute bisection
- Re: [PATCH v2 2/2] bisect: output bisect setup status in bisect log
- bisect: output bisect setup status in bisect log
- bisect: output state before we are ready to compute bisection
- bisect: status improvements when bisect is not fully fleshed out
- Re: [PATCH] bisect--helper: warn if we are assuming an unlikely pathspec
- bisect--helper: warn if we are assuming an unlikely pathspec
- http.proxy seems to not be propagated on `submodule update`