| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Matthew Kleiman <mkleiman(at)pivotal(dot)io> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: [pgaweb][patch] Use https link for git repo |
| Date: | 2017-08-29 14:45:51 |
| Message-ID: | CA+OCxoxOJ9GKD7e=naGnXdv8s676HajvT_jCzPkOvbtXx7bRpA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Tue, Aug 29, 2017 at 3:30 PM, Matthew Kleiman <mkleiman(at)pivotal(dot)io>
wrote:
> bump.
>
> On Tue, Aug 15, 2017 at 3:58 AM Matthew Kleiman <mkleiman(at)pivotal(dot)io>
> wrote:
>
>> Hi Hackers,
>>
>> As per discussion on https://www.postgresql.org/message-id/flat/CAGRPzo-_
>> dSYr5Y1D%2B0uBLo39Bb6MVTg3%3DCM%3DhrmX7LdF%3DfQbhQ%
>> 40mail.gmail.com#CAGRPzo-_dSYr5Y1D+0uBLo39Bb6MVTg3=CM=
>> hrmX7LdF=fQbhQ(at)mail(dot)gmail(dot)com, I've updated the pgadmin website with the
>> attached patch. Instead of the docs pointing developers to an ssh repo
>> link, it points them to https.
>>
>>
Hi
I prefer to keep it as git:// - I've seen caching weirdness with http(s) in
the past.
git:// is supported, and per the thread, Magnus did fix the issue seen. Is
there any other reason to change it?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2017-08-29 14:55:35 | Re: [pgaweb][patch] Use https link for git repo |
| Previous Message | Matthew Kleiman | 2017-08-29 14:30:35 | Re: [pgaweb][patch] Use https link for git repo |