Carlos Martín Nieto

@carlosmn on GitHub. Posts as cmn@elego.de.

313

messages

patches posted

58%

of 33 series merged

threads started

2011

first message, Mar 14, 2011

Apr 28, 2015

since the latest message

Messages per year

The last 24 months

Patch series

Of 33 patch series (re-rolls counted once), 19 landed on master and 14 did not.

mergeddir: allow a BOM at the beginning of exclude filesApr 16, 2015, 245e1c196d
not mergedfetch: add a failing test for prunning with overlapping refspecsFeb 27, 2014
mergedsend-pack: don't send a thin pack to a server which doesn't support itNov 23, 2013, 1ba98a79f1
not mergedthin-pack capability for send-pack/receive-packNov 6, 2013
not mergedremote: filter out invalid remote configurationsAug 27, 2013
not mergedbranch: make sure the upstream remote is configuredJul 26, 2013
not mergedpull: fail early if we know we can't merge from upstreamApr 11, 2013
mergedDocumentation/git-commit: reword the --amend explanationApr 3, 2013, aa7b8c657e
mergedconfig: don't segfault when given --path with a missing valueNov 15, 2012, 962c38eedd
not mergedrun-command: don't try to execute directoriesOct 2, 2012
mergedbranch: introduce --set-upstream-toAug 30, 2012, 6183d826ba
not mergedbranch: make --set-upstream saner without an explicit starting pointJul 5, 2012

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

Apr 28, 2015Re: curl
Apr 16, 2015Re: [PATCH] dir: allow a BOM at the beginning of exclude files
Apr 16, 2015Re: [PATCH] dir: allow a BOM at the beginning of exclude files
Apr 16, 2015Re: [PATCH] dir: allow a BOM at the beginning of exclude files
Apr 16, 2015dir: allow a BOM at the beginning of exclude files
May 19, 2014Re: Returning error message from custom smart http server
May 12, 2014Re: GIT, libcurl and GSS-Negotiate
Feb 28, 2014Re: [PATCH 2/2] fetch: handle overlaping refspecs on --prune
Feb 27, 2014Re: [PATCH 2/2] fetch: handle overlaping refspecs on --prune
Feb 27, 2014fetch: handle overlaping refspecs on --prune
Feb 27, 2014fetch: add a failing test for prunning with overlapping refspecs
Nov 23, 2013Re: [PATCH] send-pack: don't send a thin pack to a server which doesn't support it
Nov 23, 2013send-pack: don't send a thin pack to a server which doesn't support it
Nov 23, 2013Re: [PATCH 0/2] thin-pack capability for send-pack/receive-pack
Nov 6, 2013Re: [PATCH 0/2] thin-pack capability for send-pack/receive-pack
Nov 6, 2013send-pack: only send a thin pack if the server supports it
Nov 6, 2013receive-pack: advertise thin-pack
Nov 6, 2013thin-pack capability for send-pack/receive-pack
Oct 19, 2013Re: [PATCH] send-pack: don't send a thin pack when the server doesn't support it
Oct 8, 2013Re: [PATCH] send-pack: don't send a thin pack when the server doesn't support it
Oct 8, 2013send-pack: don't send a thin pack when the server doesn't support it
Aug 30, 2013Re: [PATCH] remote: filter out invalid remote configurations
Aug 27, 2013remote: filter out invalid remote configurations
Jul 26, 2013Re: [PATCH] branch: make sure the upstream remote is configured
Jul 26, 2013branch: make sure the upstream remote is configured
Jun 25, 2013Re: Basic git-archive --remote question
Apr 12, 2013Re: [PATCH] pull: fail early if we know we can't merge from upstream
Apr 11, 2013pull: fail early if we know we can't merge from upstream
Apr 5, 2013Re: [PATCH] Documentation/git-commit: reword the --amend explanation
Apr 4, 2013Re: [PATCH] Documentation/git-commit: reword the --amend explanation