Re: Problem with sources. - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Problem with sources.
Date
Msg-id 4E413AEA.50200@dunslane.net
Whole thread Raw
In response to Re: Problem with sources.  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers

On 08/09/2011 09:22 AM, Andrew Dunstan wrote:
>
>
> On 08/09/2011 09:10 AM, pasman pasmański wrote:
>> When i try to fetch sources via git, there is an error:
>>
>> error: Unable to find 676e3c735dec32ba0448fdd0faf9ace37c1fa792 under
>> http://git.postgresql.org/git/postgresql.git
>> Cannot obtain needed object 676e3c735dec32ba0448fdd0faf9ace37c1fa792
>> error: Fetch failed.
>>
>>
>> How to get current branch ?
>
>
> I always use the git protocol, which is working fine:
>
>    [andrew@ophelia ~]$ git clone
>    git://git.postgresql.org/git/postgresql.git ntestpg
>    Cloning into ntestpg...
>    remote: Counting objects: 418000, done.
>    remote: Compressing objects: 100% (78367/78367), done.
>    remote: Total 418000 (delta 348625), reused 406551 (delta 337799)
>    Receiving objects: 100% (418000/418000), 119.93 MiB | 1.13 MiB/s, 
> done.
>    Resolving deltas: 100% (348625/348625), done.
>
>


I just tested cloning over http, and it worked fine for me, although it 
took a while.

You can also pull from the clone at github, which is kept pretty up to 
date, and probably has better bandwidth, using
   git://github.com/postgres/postgres.git or   https://github.com/postgres/postgres.git

cheers

andrew



pgsql-hackers by date:

Previous
From: Joe Abbate
Date:
Subject: Re: Selecting user-defined CASTs
Next
From: Florian Pflug
Date:
Subject: Re: WIP fix proposal for bug #6123