Horton

Re: An improved README experience for PostgreSQL

Peter Eisentraut <peter@eisentraut.org>

View thread
From: Peter Eisentraut <peter@eisentraut.org>
To: Nathan Bossart <nathandbossart@gmail.com>, "David E. Wheeler" <david@justatheory.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Joe Conway <mail@joeconway.com>, Daniel Gustafsson <daniel@yesql.se>, Tom Lane <tgl@sss.pgh.pa.us>, Andrew Atkinson <andyatkinson@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Samay Sharma <samay@tembo.io>
Date: 2024-03-21T13:42:27Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add CODE_OF_CONDUCT.md, CONTRIBUTING.md, and SECURITY.md.

  2. Revise the style of a paragraph in README.md.

  3. Convert README to Markdown.

On 28.02.24 20:30, Nathan Bossart wrote:
> On Wed, Feb 28, 2024 at 01:08:03PM -0600, Nathan Bossart wrote:
>> -PostgreSQL Database Management System
>> -=====================================
>> +# PostgreSQL Database Management System
> 
> This change can be omitted, which makes the conversion even simpler.

The committed README.md contains trailing whitespace on one line:

  General documentation about this version of PostgreSQL can be found at:$
-https://www.postgresql.org/docs/devel/$
+<https://www.postgresql.org/docs/devel/>  $

If this is intentional (it could be, since trailing whitespace is 
potentially significant in Markdown), then please add something to 
.gitattributes.  Otherwise, please fix that.