Matthias Urlichs
Posts as matthias@urlichs.de, smurf@smurf.noris.de.
247
messages
23
patches posted
30%
of 20 series merged
32
threads started
2005
first message, Apr 21, 2005
Feb 10, 2026
since the latest message
Patch series
Of 20 patch series (re-rolls counted once), 6 landed on master and 14 did not.
- mergedgit-svnimport: Use separate arguments in the pipe for git-rev-parseSep 18, 2007, bf1ee63678
- mergedDon't recurse into parents marked uninteresting.Mar 9, 2006, d2c4af7373
- mergedcvsimport: Remove master-updating codeMar 7, 2006, a541211ef4
- mergedSVN import: Use one log callNov 29, 2005, 034908047d
- not mergedBuild a shared / renamed / "stable" version of the library?Sep 16, 2005
- not mergedDebian: build-depend on "bc", conflict with "git-scm"Sep 16, 2005
- mergedcvsgit fixes: spaces in filenames and CVS server dialog woesAug 15, 2005, 8b8840e046
- not mergedDebian packaging for 0.99.4Aug 13, 2005
- not mergedupdate Debian packaging for cogitoAug 11, 2005
- mergeddocument git-rev-list betterJul 29, 2005, adcd3512f5
- not mergedgit-diff-*: Allow "--name-only -z" as alias for "--name-only-z"Jul 14, 2005
- not mergeddocument CVS vs. git tagsJul 12, 2005
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: Bug: signed commits vs. git-fast-export
- Bug: signed commits vs. git-fast-export
- Re: "git checkout" safety feature
- "git checkout" obliterates not-yet-ignored files
- "git checkout" safety feature
- Re: Shallow clones with explicit history cutoff?
- Shallow clones with explicit history cutoff?
- Re: git-cvsimport - losing changes in subsequent pulls of a CVS branch that I thought I wasn't modifying in the GIT repo.
- Re: [PATCH] git-svnimport: Use separate arguments in the pipe for git-rev-parse
- Re: [PATCH] git-svnimport: Use separate arguments in the pipe for git-rev-parse
- Re: [PATCH] git-svnimport: Use separate arguments in the pipe for git-rev-parse
- git-svnimport: Use separate arguments in the pipe for git-rev-parse
- Re: Problems with git-svnimport
- Re: Git user survey and `git pull`
- Re: [PATCH] git-svnimport: Parse log message for Signed-off-by: lines
- Re: irc usage..
- Re: [PATCH] git-svnimport symlink support
- Re: [PATCH] git-svnimport symlink support
- Re: git-cvsimport "you may need to merge manually"
- Re: git-cvsimport "you may need to merge manually"
- Re: Some more cvsimport
- git-ls-files --unmerged implies --stages: ?
- "fatal: protocol error: bad line length character": ??
- Re: [PATCH] Don't recurse into parents marked uninteresting.
- Don't recurse into parents marked uninteresting.
- endless loop: ?
- Re: git-svn, tree moves, and --no-stop-on-copy
- cvsimport: Remove master-updating code
- Re: [PATCH] git-svnimport.perl: fix for 'arg list too long...'
- Re: git pull on Linux/ACPI release tree