pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: vlsi (@vlsi) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] PR #4075: docs: restructure site, compatibility page, changelog-driven releases
Date: Fri, 22 May 2026 15:55:42 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
Before I split this PR into separate "structure" and "per-page content" pieces, a practical proposal: what if I revert all prose verbatim to the version on main, in this same PR, while keeping the new page layout, navigation, styles, search, and release pipeline? The PR would then contain zero prose changes against main, matching the "no content changes" criterion you mentioned.
One thing to flag: where the new layout splits an oversized page into several, the prose would still come verbatim from the old page, sliced at existing heading boundaries with no editorial changes. New pages that have no equivalent on main (compatibility, troubleshooting) would be removed from this PR and re-added later in per-page PRs.
Would that be easier to review than starting from a fresh PR?
view thread (64+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: github://pgjdbc/pgjdbc
Cc: [email protected], [email protected]
Subject: Re: [pgjdbc/pgjdbc] PR #4075: docs: restructure site, compatibility page, changelog-driven releases
In-Reply-To: <<[email protected]>>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox