On Wed, Jul 6, 2011 at 17:59, Robert Haas wrote:
> On Wed, Jul 6, 2011 at 10:31 AM, Magnus Hagander wrote:
>> When we did the migration to git, we decided to leave the old
>> postgresql git repository around "for a while", for people who had
>> clones around it. This is the repository that was li
On Wed, 2011-07-06 at 16:31 +0200, Magnus Hagander wrote:
> When we did the migration to git, we decided to leave the old
> postgresql git repository around "for a while", for people who had
> clones around it. This is the repository that was live updated from
> cvs while we were using cvs, and doe
On Wed, Jul 06, 2011 at 04:31:53PM +0200, Magnus Hagander wrote:
> When we did the migration to git, we decided to leave the old
> postgresql git repository around "for a while", for people who had
> clones around it. This is the repository that was live updated from
> cvs while we were using cvs,
On Wed, Jul 6, 2011 at 10:31 AM, Magnus Hagander wrote:
> When we did the migration to git, we decided to leave the old
> postgresql git repository around "for a while", for people who had
> clones around it. This is the repository that was live updated from
> cvs while we were using cvs, and does
When we did the migration to git, we decided to leave the old
postgresql git repository around "for a while", for people who had
clones around it. This is the repository that was live updated from
cvs while we were using cvs, and does *not* correspond to the current
git repository when it comes to
