martin f krafft
Posts as madduck@madduck.net.
221
messages
16
patches posted
50%
of 10 series merged
59
threads started
2007
first message, Jul 9, 2007
Dec 4, 2024
since the latest message
Patch series
Of 10 patch series (re-rolls counted once), 5 landed on master and 5 did not.
- not mergedTell gitweb about repo owner via git-configFeb 3, 2010
- mergedgit-am: implement --reject option passed to git-applyJan 23, 2009, b80da424a1
- mergedImprove git-log documentation wrt file filtersSep 30, 2008, b1524ee0f3
- not mergedExport GIT_DIR after setting itMay 14, 2008
- mergedEscape project name in regexpApr 20, 2008, bbd4c307fc
- not mergedclarify need for init in git-submodules documentationAug 20, 2007
- mergedInstall man3 manpages to $PREFIX/share/man/man3 even for site installsAug 20, 2007, 191131e538
- not mergedtranslate bad characters in refnames during git-svn fetchJul 15, 2007
- mergedgit-svn init/clone --stdlayout option to default-init trunk/tags/branchesJul 14, 2007, 8f728fb96f
- not mergedfall back to mozilla's sha.h if openssl/sha.h is not availableJul 14, 2007
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
- git-daemon not consulting ~/.gitconfig
- gitweb: Exiting subroutine via next at /usr/lib/cgi-bin/gitweb.cgi line 3142
- Re: [PATCH] checkout: be quiet if not on isatty()
- Tracking topic branches with rebases vs. merges (was: Branch dependencies)
- TopGit with rebased branches, problems with publishing (was: Branch dependencies)
- changing the set of dependencies (was: Branch dependencies)
- Re: per-ref data storage
- per-ref data storage (was: Storing additional information in commit headers)
- Re: working prototype of orphan parent commits as datastores (was: Storing additional information in commit headers)
- Re: working prototype of orphan parent commits as datastores (was: Storing additional information in commit headers)
- Re: Branch dependencies
- Re: Storing additional information in commit headers
- working prototype of orphan parent commits as datastores (was: Storing additional information in commit headers)
- Re: Storing additional information in commit headers
- Re: Storing additional information in commit headers
- Re: Storing additional information in commit headers
- Re: Storing additional information in commit headers
- Re: Storing additional information in commit headers
- Re: Storing additional information in commit headers
- Storing additional information in commit headers
- Branch dependencies
- git submodule add requires remote
- Re: Import existing (old) topic branches in topgit
- Re: Find the next tag on a given branch
- Find the next tag on a given branch
- Re: URL substitution and config file precedence
- URL substitution and config file precedence
- Re: Using trees for metatagging
- Re: Using trees for metatagging
- Re: Using trees for metatagging