History doc page clarification on naming

Started by Dave Pageabout 1 year ago5 messageshackers
Jump to latest
#1Dave Page
dpage@pgadmin.org

Further to my previous patch to update the licence preamble (
/messages/by-id/CA+OCxoy1Z05qDb1BfZZaVzT=6BrEW6u3wxprBkc7pewThJMoCA@mail.gmail.com),
the attached patch updates the history doc page to properly reflect the use
of the name "Postgres".

Text by Jonathan Katz, I just turned it into a patch.

This should be backpatched to all supported branches.

--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com

Attachments:

project_name_clarification_v1.diffapplication/octet-stream; name=project_name_clarification_v1.diffDownload+4-5
#2Daniel Gustafsson
daniel@yesql.se
In reply to: Dave Page (#1)
Re: History doc page clarification on naming

On 6 Mar 2025, at 12:05, Dave Page <dpage@pgadmin.org> wrote:

Further to my previous patch to update the licence preamble (/messages/by-id/CA+OCxoy1Z05qDb1BfZZaVzT=6BrEW6u3wxprBkc7pewThJMoCA@mail.gmail.com), the attached patch updates the history doc page to properly reflect the use of the name "Postgres".

Text by Jonathan Katz, I just turned it into a patch.

LGTM, tested and it compiles cleanly.

This should be backpatched to all supported branches.

I can help you apply it once a few more timezones have had a chance to nitpick.

--
Daniel Gustafsson

#3Dave Page
dpage@pgadmin.org
In reply to: Daniel Gustafsson (#2)
Re: History doc page clarification on naming

On Thu, 6 Mar 2025 at 12:19, Daniel Gustafsson <daniel@yesql.se> wrote:

On 6 Mar 2025, at 12:05, Dave Page <dpage@pgadmin.org> wrote:

Further to my previous patch to update the licence preamble (

/messages/by-id/CA+OCxoy1Z05qDb1BfZZaVzT=6BrEW6u3wxprBkc7pewThJMoCA@mail.gmail.com),
the attached patch updates the history doc page to properly reflect the use
of the name "Postgres".

Text by Jonathan Katz, I just turned it into a patch.

LGTM, tested and it compiles cleanly.

This should be backpatched to all supported branches.

I can help you apply it once a few more timezones have had a chance to
nitpick.

Thank you!

--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com

#4Daniel Gustafsson
daniel@yesql.se
In reply to: Dave Page (#3)
Re: History doc page clarification on naming

On 6 Mar 2025, at 14:12, Dave Page <dpage@pgadmin.org> wrote:
On Thu, 6 Mar 2025 at 12:19, Daniel Gustafsson <daniel@yesql.se <mailto:daniel@yesql.se>> wrote:

On 6 Mar 2025, at 12:05, Dave Page <dpage@pgadmin.org <mailto:dpage@pgadmin.org>> wrote:

Further to my previous patch to update the licence preamble (/messages/by-id/CA+OCxoy1Z05qDb1BfZZaVzT=6BrEW6u3wxprBkc7pewThJMoCA@mail.gmail.com), the attached patch updates the history doc page to properly reflect the use of the name "Postgres".

Text by Jonathan Katz, I just turned it into a patch.

LGTM, tested and it compiles cleanly.

This should be backpatched to all supported branches.

I can help you apply it once a few more timezones have had a chance to nitpick.

Thank you!

That ended up being an extended set of timezones allowed but finally got to
pushing this backpatched to all supported branches,

--
Daniel Gustafsson

#5Dave Page
dpage@pgadmin.org
In reply to: Daniel Gustafsson (#4)
Re: History doc page clarification on naming

On Sun, 6 Apr 2025 at 23:51, Daniel Gustafsson <daniel@yesql.se> wrote:

On 6 Mar 2025, at 14:12, Dave Page <dpage@pgadmin.org> wrote:
On Thu, 6 Mar 2025 at 12:19, Daniel Gustafsson <daniel@yesql.se> wrote:

On 6 Mar 2025, at 12:05, Dave Page <dpage@pgadmin.org> wrote:

Further to my previous patch to update the licence preamble (

/messages/by-id/CA+OCxoy1Z05qDb1BfZZaVzT=6BrEW6u3wxprBkc7pewThJMoCA@mail.gmail.com),
the attached patch updates the history doc page to properly reflect the use
of the name "Postgres".

Text by Jonathan Katz, I just turned it into a patch.

LGTM, tested and it compiles cleanly.

This should be backpatched to all supported branches.

I can help you apply it once a few more timezones have had a chance to
nitpick.

Thank you!

That ended up being an extended set of timezones allowed but finally got to
pushing this backpatched to all supported branches,

Thank you!

--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com