From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
---|---|
To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
Cc: | Neil Tiffin <neilt(at)neiltiffin(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Stephen Frost <sfrost(at)snowman(dot)net>, Josh Drake <jd(at)commandprompt(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: RFC: Remove contrib entirely |
Date: | 2015-06-05 17:51:18 |
Message-ID: | 5E3EDC12-D53A-490A-8778-4A110C8103D4@justatheory.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jun 5, 2015, at 10:47 AM, Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> wrote:
>> Right. Just stick it in your README.
>>
>> http://blog.pgxn.org/post/116087351668/badges
>
> I meant something more integrated with PGXN itself, such as what you're proposing for pgxn-tester. That would allow for things like PGXN search results to show Travis results.
Well, it’s not really possible to tell if there’s a Travis job for a project. I could add something to the META.json, though.
David
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-06-05 17:59:36 | Re: Is it possible to have a "fast-write" Index? |
Previous Message | Andrew Dunstan | 2015-06-05 17:51:07 | Re: Further issues with jsonb semantics, documentation |