Matt McCutchen
@mattmccutchen on GitHub. Posts as hashproduct@gmail.com, matt@mattmccutchen.net.
113
messages
42
patches posted
74%
of 23 series merged
35
threads started
2006
first message, Aug 27, 2006
Aug 4, 2020
since the latest message
Patch series
Of 23 patch series (re-rolls counted once), 17 landed on master and 6 did not.
- mergedfetch: print an error when declining to request an unadvertised objectv2, Feb 22, 2017, e70a65c5d8
- mergedmerge-recursive: make "CONFLICT (rename/delete)" message show both pathsJan 28, 2017, b26d87f2da
- mergedt0001: don't let a default ACL interfere with the umask testJan 28, 2017, d549d21307
- mergedgit-gc.txt: expand discussion of races with other processesNov 15, 2016, f1350d0c12
- mergedfetch/push: document that private data can be leakedNov 14, 2016, 235ec24352
- not mergedgit.txt: encourage bug reporters to test recent versionsFeb 9, 2016
- mergedDocumentation/git-clean.txt: don't mention deletion of .git/modules/*Feb 6, 2016, 31e3c2d7f8
- not mergedMakefile: move -Wall from CFLAGS to BASIC_CFLAGSApr 6, 2010
- mergedgitweb: add $prevent_xss option to prevent XSS by repository contentFeb 8, 2009, 7e1100e9e9
- not mergedgitweb: allow access to forks with strict_exportDec 13, 2008
- not mergedgitweb: support hiding projects from user-visible listsDec 13, 2008
- not mergedgitweb: Add option to put a trailing slash on pathinfo-style project URLsDec 13, 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: Renaming the "master" branch without breaking existing clones
- Re: Renaming the "master" branch without breaking existing clones
- Re: Renaming the "master" branch without breaking existing clones
- Renaming the "master" branch without breaking existing clones
- Re: Duplicate safecrlf warning for racily clean index entry
- Re: Duplicate safecrlf warning for racily clean index entry
- Duplicate safecrlf warning for racily clean index entry
- Tools that do an automatic fetch defeat "git push --force-with-lease"
- Re: [PATCH 1/3] fetch-pack: move code to report unmatched refs to a function
- fetch_refs_via_pack: call report_unmatched_refs
- fetch-pack: add specific error for fetching an unadvertised object
- fetch-pack: move code to report unmatched refs to a function
- fetch-pack: add specific error for fetching an unadvertised object
- fetch-pack: move code to report unmatched refs to a function
- fetch_refs_via_pack: call report_unmatched_refs
- Re: [PATCH] fetch: print an error when declining to request an unadvertised object
- fetch: print an error when declining to request an unadvertised object
- Re: [PATCH] fetch: print an error when declining to request an unadvertised object
- Re: [PATCH] fetch: print an error when declining to request an unadvertised object
- fetch: print an error when declining to request an unadvertised object
- Re: [PATCH] merge-recursive: make "CONFLICT (rename/delete)" message show both paths
- merge-recursive: make "CONFLICT (rename/delete)" message show both paths
- t0001: don't let a default ACL interfere with the umask test
- "git diff --ignore-space-change --stat" lists files with only whitespace differences as "changed"
- Re: Protecting old temporary objects being reused from concurrent "git gc"?
- git-gc.txt: expand discussion of races with other processes
- Re: Protecting old temporary objects being reused from concurrent "git gc"?
- Protecting old temporary objects being reused from concurrent "git gc"?
- Re: "git subtree --squash" interacts poorly with revert, merge, and rebase
- Re: [PATCH] fetch/push: document that private data can be leaked