Felipe Contreras

@felipec on GitHub. Posts as felipe.contreras@gmail.com.

6,566

messages

2,924

patches posted

49%

of 226 series merged

614

threads started

2008

first message, Aug 22, 2008

May 13, 2023

since the latest message

Messages per year

The last 24 months

Patch series

Of 226 patch series (re-rolls counted once), 110 landed on master and 116 did not.

not mergedtest: mergetool: unset environment variableMay 13, 2023
not mergedlib: add new libgit-builtinMay 12, 2023
not mergeddiff: fix -s and --no-patchMay 12, 2023
not mergedFix merge_recursive_config()May 12, 2023
not mergedmerge-tree: load config correctlyMay 11, 2023
not mergedGeneric conflict style fixesv3, May 10, 2023
mergedtest: rev-parse-upstream: add missing cmpMay 9, 2023, 159f4b9c3b
not mergeddoc: revisions: fixes and cleanupsMay 4, 2023
not mergeddoc: manpage: get rid of an ancient asciidoc workaroundMay 4, 2023
not mergeddoc: remove unnecessary newline from calloutsMay 3, 2023
mergeddoc: doc-diff: specify dateMay 3, 2023, 1c301bcaa5
mergeddoc: manpage: remove maximum title lengthv2, May 3, 2023, d832f2ac55

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

May 13, 2023test: mergetool: unset environment variable
May 13, 2023Re: [PATCH v2] diff: fix interaction between the "-s" option and other options
May 13, 2023Re: [PATCH v2] diff: fix interaction between the "-s" option and other options
May 12, 2023Re: Can we clarify the purpose of `git diff -s`?
May 12, 2023Re: Can we clarify the purpose of `git diff -s`?
May 12, 2023lib: add new libgit-builtin
May 12, 2023Re: Can we clarify the purpose of `git diff -s`?
May 12, 2023Re: Can we clarify the purpose of `git diff -s`?
May 12, 2023Re: Can we clarify the purpose of `git diff -s`?
May 12, 2023Re: Can we clarify the purpose of `git diff -s`?
May 12, 2023Re: Can we clarify the purpose of `git diff -s`?
May 12, 2023Re: Can we clarify the purpose of `git diff -s`?
May 12, 2023Re: [PATCH v1 0/7] diff: fix -s and --no-patch
May 12, 2023diff: remove DIFF_FORMAT_NO_OUTPUT
May 12, 2023diff: add --silent as alias of -s
May 12, 2023diff: split --no-patch from -s
May 12, 2023test: add various tests for diff formats with -s
May 12, 2023diff: make DIFF_FORMAT_NO_OUTPUT 0
May 12, 2023diff: introduce DIFF_FORMAT_DEFAULT
May 12, 2023diff: fix -s and --no-patch
May 12, 2023line-log: set patch format explicitly by default
May 12, 2023Re: What's cooking in git.git (May 2023, #04; Thu, 11)
May 12, 2023Re: What's cooking in git.git (May 2023, #04; Thu, 11)
May 12, 2023Fix merge_recursive_config()
May 11, 2023Re: Can we clarify the purpose of `git diff -s`?
May 11, 2023Re: [PATCH] merge-tree: load default git config
May 11, 2023merge-tree: load config correctly
May 11, 2023Re: Can we clarify the purpose of `git diff -s`?
May 11, 2023Re: Can we clarify the purpose of `git diff -s`?
May 11, 2023Re: Can we clarify the purpose of `git diff -s`?