[pgrouting-dev] develop_2_1_0 back again.

Stephen Woodbridge woodbri at swoodbridge.com
Sat Jul 25 06:28:56 PDT 2015


On 7/25/2015 2:09 AM, Vicky Vergara wrote:
>
> Hello all,
>
> I reverted develop_2_1_0 to a stable state.
> Sorry if that caused any inconvinience.

Hi Vicky,

I'm not sure what I need to do to update my system. I did the following:

> [develop] ~/work/pgrouting$ git pull
> Enter passphrase for key '/home/woodbri/.ssh/id_rsa':
> From github.com:pgRouting/pgrouting
>  + 7f3e172...74943ff develop_2_1_0 -> origin/develop_2_1_0  (forced update)
> Already up-to-date.
> [develop] ~/work/pgrouting$ git checkout develop_2_1_0
> Switched to branch 'develop_2_1_0'
> Your branch is ahead of 'origin/develop_2_1_0' by 14 commits.
>   (use "git push" to publish your local commits)
> [develop_2_1_0.] ~/work/pgrouting$ git pull
> Enter passphrase for key '/home/woodbri/.ssh/id_rsa':
> Already up-to-date.

but my develop_2_1_0 branch still has the old broken files and I don't 
think I should push them.

Are other users seeing something similar?

-Steve



More information about the pgrouting-dev mailing list