The "View Tickets" gizmo via trac is busted: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 406, in dispatch_request dispatcher.dispatch(req) ... [More] File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 237, in dispatch resp = chosen_handler.process_request(req) File "/usr/lib/python2.4/site-packages/trac/ticket/report.py", line 88, in process_request resp = self._render_view(req, db, id) File "/usr/lib/python2.4/site-packages/trac/ticket/report.py", line 332, in _render_view absurls=(format == 'rss')) File "/usr/lib/python2.4/site-packages/trac/wiki/formatter.py", line 1001, in wiki_to_html Formatter(env, req, absurls, db).format(wikitext, out, escape_newlines) File "/usr/lib/python2.4/site-packages/trac/wiki/formatter.py", line 824, in format result = re.sub(self.wiki.rules, self.replace, line) File "/usr/lib/python2.4/sre.py", line 142, in sub return _compile(pattern, 0).sub(repl, string, count) File "/usr/lib/python2.4/site-packages/trac/wiki/formatter.py", line 770, in replace replacement = self.handle_match(fullmatch) File "/usr/lib/python2.4/site-packages/trac/wiki/formatter.py", line 763, in handle_match return external_handler(self, match, fullmatch) File "/usr/lib/python2.4/site-packages/trac/versioncontrol/web_ui/changeset.py", line 697, in y, z)) File "/usr/lib/python2.4/site-packages/trac/versioncontrol/web_ui/changeset.py", line 715, in _format_changeset_link changeset = self.env.get_repository().get_changeset(rev) File "build/bdist.linux-x86_64/egg/gitplugin/git_fs.py", line 63, in get_changeset File "build/bdist.linux-x86_64/egg/gitplugin/git_fs.py", line 189, in __init__ File "build/bdist.linux-x86_64/egg/gitplugin/PyGIT.py", line 77, in read_commit IndexError: pop from empty list [Less]

hg-fast-export.sh from git-fast-export (available at repo.or.cz) works wonderfully. You need a local hg repository, but then you just dump to git and use your standard tools...

Even with distributed systems... The committer can be credited with some review and control, and the author with writing...

If the project containts GNU-formatted ChangeLog files, those are the place to look for who contributed which change...

I'd look into PEG & packrat parsing for practical Fortran use. With simple preprocessing (guessing fixed/free format, separating the first six columns of fixed-format, guessing the required line ... [More] length, etc.), you should be able to rip open most extant Fortran code. Technically, PEG could manage the first six columns in the grammar proper, but I wouldn't even try. [Less]

Any hope of Fortran support?