* Tatsuo Ishii <ishii@postgresql.org> [080527 10:12]:
> I don't stick to CVS at all. If contributors are comfortable, let's go
> with GIT.
>
> BTW, does this setting requrie a local GIT server be installed? If so,
> that might be a problem for me since I don't have resource for that.
GIT is a completely distributed VCS/SCM. This means that every single
local clone of a repository is a completely self-sufficent repository.
So you never need to have a "local server" to do anything in GIT.
When people think of "git servers", they are generally thinking of 2
things:
1) Gitweb - the "web interface" to a git repo
2) "public repositories" via git:// git protocol
Neither of these are necessary to use git "locally", but are means for
exchaning/sharing the current state of a repository.
The git protocol is a normal send/receive transfer mechanism, of the
same sort as CVS. Most people using git use it over SSH when pushing
their changes to public places. The git-daemon server serves the
"git://" protocol over any port (usually 9418) and is a way to give
anonymous access to a git repo (usually read-only, but can be
read-write) without needing to give SSH access, like cvs pserver.
But the short of it is, git.postgresql.org runs both gitweb and
git-daemon for you, so if you want to use git, all you need is a local
git package, and SSH access to git.postgresql.org, which can do all the
public serving/sharing for you.
I guess I should have had a GIT talk/intro/anything over lunch or
something last week at PGCon. I hadn't thought of it then... Bummer...
a.
--
Aidan Van Dyk Create like a god,
aidan@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
