Re: WITH RECURSIVE patches V0.1 TODO items

From: Aidan Van Dyk <aidan(at)highrise(dot)ca>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: stark(at)enterprisedb(dot)com, andrew(at)dunslane(dot)net, david(at)fetter(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: WITH RECURSIVE patches V0.1 TODO items
Date: 2008-05-27 14:50:11
Message-ID: 20080527145011.GI2108@yugib.highrise.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Tatsuo Ishii <ishii(at)postgresql(dot)org> [080527 10:40]:

> In my understanding, yes.

If you want to push back to the same location, yes, you'll all need
accounts at the same location giving you permission to push there.

Technically, you could all "share" an account there too, but the
drawbacks to lack of accountability usually mean separate accounts is a
better solution.

> And I think even if we would have accounts on the community git
> server, we cannot push (commit) to the repository. Probably all we can
> do is, get the diff between someone's pushed data and the origin.

No, it's easy to set it up so you can directly push to a shared
repository, or each push to your individual repositories and
"pull/merge" others changes into your own. Or any combination of the
above.

a.
--
Aidan Van Dyk Create like a god,
aidan(at)highrise(dot)ca command like a king,
http://www.highrise.ca/ work like a slave.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-05-27 16:20:45 Hiding undocumented enum values?
Previous Message David Fetter 2008-05-27 14:48:30 Re: WITH RECURSIVE patches V0.1 TODO items