Would this work for commits? Assuming of course that I had rights to
commit?

>
>>
>> If this isn't supposed to be edited by devs at large, then somebody can
>> feel free to close that bug. It had been open for ages so I figured I
>> might just see if I could take care of it.
>
> Attach a patch to bug. That repo is not open for anyone to commit to,
> you have to be a member of the QA team, (or approval from Halcy0n or
> Betelguese)

Makes sense. That would be the issue in this case.
My general point was that documentation in general around git is very
vague, except for the overlays (which is still lacking, but there is
enough info to at least be dangerous there).
Maybe a worked example with full command lines might be helpful -
starting from scratch check out repository, change a file, and commit it
to the official repository. The info out there does require filling in
a lot of blanks, and since git itself has no concept of a central
repository there aren't a lot of examples of how to do this. Such an
example should of course factor in any Gentoo-isms as well (changelogs
(if applicable), commit messages, etc - anything we ought to be doing).
Rich