Re: [pgsql-www] Where to put shared designs/images
| От | Magnus Hagander |
|---|---|
| Тема | Re: [pgsql-www] Where to put shared designs/images |
| Дата | |
| Msg-id | CABUevExACTwWLtm3R+rUqW-pu890-UmGKdMUndgg69qvx8-QSw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [pgsql-www] Where to put shared designs/images (Stephen Frost <sfrost@snowman.net>) |
| Ответы |
Re: [pgsql-www] Where to put shared designs/images
Re: [pgsql-www] Where to put shared designs/images |
| Список | pgsql-advocacy |
On Tue, Feb 11, 2014 at 3:39 AM, Stephen Frost <sfrost@snowman.net> wrote:
* Michael Paquier (michael.paquier@gmail.com) wrote:
> On Tue, Feb 11, 2014 at 10:10 AM, Josh Berkus <josh@agliodbs.com> wrote:> > So I'm happy with github as a choice. However, I don't know thatI thought they *used* to, but dropped it due to issues..?
> > there's any way to do "link to the latest version of raw file X", so
> > we'd still want to publish stuff to FTP.postgresql.org, no?
> >
> > Probably not everything, though -- if we were selective, we'd avoid the
> > space issue.
> AFAIK, github supports such URLs, aka linking to the latest version of
> a file on a branch:
They disabled "uploads", separate from the repositories, was my understanding: https://github.com/blog/1302-goodbye-uploads
Not sure about predictable URLs, but using git itself for very large repos is maybe not the best idea in general. Everybody will have to clone a 10+Gb repository to contribute even something simple, I'm not sure that's very contributor-friendly either...
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
В списке pgsql-advocacy по дате отправления: