Now a new feature release is out, it's a good time to welcome new

people to the list.  This message talks about how git.git is managed,

and how you can work with it.
* IRC and Mailing list
Many active members of development community hang around on #git

IRC channel on Freenode.  Its log is available at:
        http://colabti.de/irclogger/irclogger_log/git
The development however is primarily done on this mailing list

you are reading right now.  If you have patches, please send

them to the list, following Documentation/SubmittingPatches.
I usually try to read all patches posted to the list, and follow

almost all the discussions on the list, unless the topic is about an

obscure corner that I do not personally use.  But I am obviously not

perfect.  If you sent a patch that you did not hear from anybody for

three days, that is a very good indication that it was dropped on the

floor --- please do not hesitate to remind me.
The list archive is available at a few public sites as well:
        http://news.gmane.org/gmane.comp.version-control.git/

        http://marc.theaimsgroup.com/?l=git

        http://www.spinics.net/lists/git/
and some people seem to prefer to read it over NNTP:
        nntp://news.gmane.org/gmane.comp.version-control.git
When you point at a message in a mailing list archive, using

gmane is often the easiest to follow by readers, like this:
        http://thread.gmane.org/gmane.comp.version-control.git/27/focus=217
as it also allows people who subscribe to the mailing list as

gmane newsgroup to "jump to" the article.
* Repositories, branches and documentation.
My public git.git repository is at:
        git://git.kernel.org/pub/scm/git/git.git/
Immediately after I publish to the primary repository at kernel.org, I

also push into an alternate here:
        git://repo.or.cz/alt-git.git/
Impatient people might have better luck with the latter one.
Their gitweb interfaces are found at:
        [ message continues ]