I agree; I am not aware of any generic way of finding out who forked what repo and what it contains.
There can't be in the general case. For example, you could clone a repo and take your machine off the Known Net; even if your IP address was recorded, it wouldn't help.
In any case, it took long enough for the SRFI process to accept git, imperfect as it is; I wouldn't want to supersede it. Here's my favorite remarks about git, from the Plan 9 git filesystem's README:
The most obvious difference is that Git's index is a bit boneheaded, so I'm
ignoring it. The index doesn't affect the wire protocol, so this
isn't an interoperability issue, unless you share the same physical
repository on both Plan 9 and Unix. If you do, expect them to disagree
about the files that have been modified in the working copy.
In fact, the entire concept of the staging area has been dropped, as
it's both confusing and clunky. There are now only three states that
files can be in: 'untracked', 'dirty', and 'committed'. Tracking is
done with empty files under .git/index9/{removed,tracked}/path/to/file.
In addition to the FS proper, there are also programs to execute various git operations: add, branch,conf, clone, commit, diff, export, import, init, log, merge, pull, push, query, revert, rm, walk. They are mostly short and simple shell (rc) scripts, and you certainly don't need to use them.
If you are allergic to github,
there are other forges and ways to convert between them.
John Cowan
http://vrici.lojban.org/~cowan xxxxxx@ccil.orgAnd through this revolting graveyard of the universe the muffled,
maddening beating of drums, and thin, monotonous whine of blasphemous
flutes from inconceivable, unlighted chambers beyond Time; the
detestable pounding and piping whereunto dance slowly, awkwardly, and
absurdly the gigantic tenebrous ultimate gods --the blind, voiceless,
mindless gargoyles whose soul is Nyarlathotep. (Lovecraft)