| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Atkinson <andyatkinson(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, samay(at)tembo(dot)io |
| Subject: | Re: An improved README experience for PostgreSQL |
| Date: | 2024-02-28 19:07:30 |
| Message-ID: | AB5180DD-4F1E-447B-BE5A-471CBBDB839F@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 28 Feb 2024, at 19:51, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>
> On 2024-Feb-28, Joe Conway wrote:
>
>> Markdown is pretty readable as text, I'm not sure why we need both.
>
> *IF* people don't go overboard, yes. I agree, but let's keep an eye so
> that it doesn't become an unreadable mess. I've seen some really
> horrible markdown files that I'm sure most of you would object to.
Absolutely, I agree. Considering the lengths we go to to keep our code readable I’m not worried, I expect that a markdown README would end up pretty close to the txt version we have today.
./daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-02-28 19:08:03 | Re: An improved README experience for PostgreSQL |
| Previous Message | Tom Lane | 2024-02-28 19:06:44 | Re: Fix for edge case in date_bin() function |