Pierre Habouzit
@MadCoder on GitHub. Posts as madcoder@debian.org.
952
messages
260
patches posted
55%
of 77 series merged
90
threads started
2006
first message, Aug 23, 2006
May 6, 2011
since the latest message
Patch series
Of 77 patch series (re-rolls counted once), 42 landed on master and 35 did not.
- not mergedstatus: display "doing what" information in git statusv2, May 6, 2011
- mergedfix git branch -m in presence of cross devicesJul 7, 2010, 765c22588d
- not mergedupdate gitignoreSep 16, 2009
- not mergedgit-add -p: be able to undo a given hunkJul 23, 2009
- mergedjanitor: useless checks before freeJul 22, 2009, 24deea5273
- mergedjanitor: use NULL and not 0 for pointers.Jul 22, 2009, 67da52bedc
- mergedparse-options: add parse_options_check to validate option specs.Jun 9, 2009, cb9d398c35
- mergedhook/update: example of how to prevent branch creationApr 16, 2009, aed97c677c
- mergedAvoid spurious error messages on error mistakes.Jan 12, 2009, 12dd111288
- not mergedstrbuf_readlink semantics update.Dec 23, 2008
- mergedgit send-email: avoid leaking directory file descriptors.Nov 10, 2008, 8c17868795
- not mergedprepare deprecation of git-revertOct 31, 2008
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 v2] status: display "doing what" information in git status
- Re: [PATCH v2] status: display "doing what" information in git status
- Re: [PATCH v2] status: display "doing what" information in git status
- Re: [PATCH 1/1] status: display "doing what" information in git status
- status: display "doing what" information in git status
- Re: [PATCH 1/1] status: display "doing what" information in git status
- Re: [PATCH 1/1] status: display "doing what" information in git status
- Re: [PATCH 1/1] status: display "doing what" information in git status
- Re: [PATCH 1/1] status: display "doing what" information in git status
- status: display "doing what" information in git status
- Re: [RFC PATCH 0/2] Allow detached forms (--option arg) for git log options.
- Re: [RFC PATCH 0/2] Allow detached forms (--option arg) for git log options.
- Re: [RFC PATCH 0/2] Allow detached forms (--option arg) for git log options.
- Re: [PATCH] rev-parse: fix --parse-opt --keep-dashdash --stop-at-non-option
- fix git branch -m in presence of cross devices
- Re: Using test-lib.sh under GPLv3?
- Re: [PATCH 1/1] update gitignore
- update gitignore
- git-add -p: be able to undo a given hunk
- janitor: useless checks before free
- janitor: add DIV_ROUND_UP and use it.
- refactor: use bitsizeof() instead of 8 * sizeof()
- janitor: use NULL and not 0 for pointers.
- janitoring
- parse-options: add parse_options_check to validate option specs.
- hook/update: example of how to prevent branch creation
- Avoid spurious error messages on error mistakes.
- Re: current git kernel has strange problems during bisect
- Re: [PATCH] filter-branch: add git_commit_non_empty_tree and --prune-empty.
- Re: [PATCH] filter-branch: add git_commit_non_empty_tree and --prune-empty.