Marc Branchaud
@marcnarc on GitHub. Posts as marcnarc@xiplink.com.
471
messages
70
patches posted
21%
of 29 series merged
31
threads started
2008
first message, Oct 16, 2008
Feb 25, 2026
since the latest message
Patch series
Of 29 patch series (re-rolls counted once), 6 landed on master and 23 did not.
- not mergednew-workdir: Never try to recurse into submodules on the initial checkout.Jan 14, 2019
- not mergedfetch: Ensure that fetch.recurseSubmodules overrides submodule.recurse.Sep 21, 2018
- mergedMake diff plumbing commands respect the indentHeuristic.v4, May 8, 2017, cf5e77223a
- not mergedTweak help auto-correct phrasing.Dec 19, 2016
- not mergedRelease note spelling and phrasing fixups.Nov 24, 2016
- not mergedBUG: indent-with-non-tab always on (was: Re: [PATCH v6 00/12] Update git revisions)v6, Aug 15, 2016
- not mergedgitk: Use translated version of "Command line" in getcommitlines.Apr 7, 2015
- not mergedTweaking the gitk window title.Mar 23, 2015
- not mergedRelNotes: Spelling & grammar tweaks.Nov 21, 2014
- not mergedRelease notes grammatical fixes.Aug 5, 2014
- mergeddocs: Explain the purpose of fetch's and pull's <refspec> parameter.Jun 11, 2014, db4e4113ea
- not mergedfetch doc: Move FETCH_HEAD material, and add an example.Jun 2, 2014
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: --no-decorate and %d in git-log(1)
- Re: --no-decorate and %d in git-log(1)
- Re: [PATCH v5] build: regenerate config-list.h when Documentation changes
- Re: The SHA256 of "xy\n" (ASCII, no CRLF) contains 1337, ACBAD in za, and I am 1aa
- Re: git fails to checkout SHA1 submodule in SHA256 repo with --depth=1
- Re: git-subtree documentation fix request: split example causes fatal error
- Re: gitk: visually indicate whether a tag exists on a remote
- Re: [PATCH] portability: allow building in systems without d_type
- Re: [PATCH RFC 0/5] Introduce git-blame-tree(1) command
- Re: [PATCH RFC 0/5] Introduce git-blame-tree(1) command
- Re: [PATCH RFC 0/5] Introduce git-blame-tree(1) command
- Re: [PATCH RFC 0/5] Introduce git-blame-tree(1) command
- Re: [PATCH RFC 0/5] Introduce git-blame-tree(1) command
- Re: [PATCH RFC 0/5] Introduce git-blame-tree(1) command
- Re: [PATCH RFC 0/5] Introduce git-blame-tree(1) command
- Re: [PATCH RFC 0/5] Introduce git-blame-tree(1) command
- Re: [PATCH RFC 0/5] Introduce git-blame-tree(1) command
- Re: General output formatting
- General output formatting (was: Re: \b character escapes in CLI usage)
- Re: [Q] rebase -i: turn "pick" to "edit", make no change, what should happen?
- Re: [PATCH] gitk: add "Hightlight commit name" menu entry
- Re: [PATCH] gitk: add "Hightlight commit name" menu entry
- sshd support for Git protocol v2 (was: Re: Name for initial branch is ignored when repository is cloned with SSH)
- Re: git-gui desktop launcher
- Re: Storing private config files in .git directory?
- Re: [PATCH v3] git-rebase.txt: rewrite docu for fixup/squash (again)
- Re: using oldest date when squashing commits
- Re: using oldest date when squashing commits
- Re: [PATCH v3] git-rebase.txt: rewrite docu for fixup/squash (again)
- Re: [RESEND v2] git-rebase.txt: rewrite docu for fixup/squash (again)