Git is not an acronym
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t77016psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 27, 2026 at 04:48 PM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t77016_1 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t77016_1 && git checkout t77016_1Patchset v1 (message #1) is on t77016_1
Commit 651377933e031 cleaned up references to CVS replacing them with Git.
Replacing CVS with Git in acronyms.sgml seems a bit incorrect though as Git
isn't an acronym (but CVS is, hence the original item replaced). We also never
refer to Git with <acronym /> tags. The attached removes Git from the acronyms
page.
--
Daniel Gustafsson https://vmware.com/
On 6/10/21 7:40 AM, Daniel Gustafsson wrote:
Commit 651377933e031 cleaned up references to CVS replacing them with Git.
Replacing CVS with Git in acronyms.sgml seems a bit incorrect though as Git
isn't an acronym (but CVS is, hence the original item replaced). We also never
refer to Git with <acronym /> tags. The attached removes Git from the acronyms
page.
According to the README[1]https://github.com/git/git/blob/master/README.md and reference in the Wikipedia page that our
docs point too, "git" can be an acronym based on context. I don't think
it's harmful to leave it in.
Jonathan
On Thu, 10 Jun 2021 at 09:04, Jonathan S. Katz <jkatz@postgresql.org> wrote:
On 6/10/21 7:40 AM, Daniel Gustafsson wrote:
Commit 651377933e031 cleaned up references to CVS replacing them with
Git.
Replacing CVS with Git in acronyms.sgml seems a bit incorrect though as
Git
isn't an acronym (but CVS is, hence the original item replaced). We
also never
refer to Git with <acronym /> tags. The attached removes Git from the
acronyms
page.
According to the README[1] and reference in the Wikipedia page that our
docs point too, "git" can be an acronym based on context. I don't think
it's harmful to leave it in.
Doesn't seem like a nit worth picking to me either.
Dave
Show quoted text
On 10 Jun 2021, at 15:03, Jonathan S. Katz <jkatz@postgresql.org> wrote:
On 6/10/21 7:40 AM, Daniel Gustafsson wrote:
Commit 651377933e031 cleaned up references to CVS replacing them with Git.
Replacing CVS with Git in acronyms.sgml seems a bit incorrect though as Git
isn't an acronym (but CVS is, hence the original item replaced). We also never
refer to Git with <acronym /> tags. The attached removes Git from the acronyms
page.According to the README[1] and reference in the Wikipedia page that our
docs point too, "git" can be an acronym based on context. I don't think
it's harmful to leave it in.
Not harmful, but an acronym which we explain with the acronym itself doesn't
seem like helpful use of page real-estate.
--
Daniel Gustafsson https://vmware.com/
you mean something like Gnu s Not Unix ?
Marc MILLAS
Senior Architect
+33607850334
www.mokadb.com
On Thu, Jun 10, 2021 at 3:34 PM Daniel Gustafsson <daniel@yesql.se> wrote:
Show quoted text
On 10 Jun 2021, at 15:03, Jonathan S. Katz <jkatz@postgresql.org> wrote:
On 6/10/21 7:40 AM, Daniel Gustafsson wrote:
Commit 651377933e031 cleaned up references to CVS replacing them with
Git.
Replacing CVS with Git in acronyms.sgml seems a bit incorrect though as
Git
isn't an acronym (but CVS is, hence the original item replaced). We
also never
refer to Git with <acronym /> tags. The attached removes Git from the
acronyms
page.
According to the README[1] and reference in the Wikipedia page that our
docs point too, "git" can be an acronym based on context. I don't think
it's harmful to leave it in.Not harmful, but an acronym which we explain with the acronym itself
doesn't
seem like helpful use of page real-estate.--
Daniel Gustafsson https://vmware.com/
On Thu, 10 Jun 2021 at 08:34, Daniel Gustafsson <daniel@yesql.se> wrote:
Not harmful, but an acronym which we explain with the acronym itself doesn't
seem like helpful use of page real-estate.
Perhaps I am missing something. The two acronyms offered appear to be:
"global information tracker": you're in a good mood, and it actually
works for you. Angels sing, and a light suddenly fills the room.
"goddamn idiotic truckload of sh*t": when it breaks
I don't personally care all that much whether it stays or goes at
present, but again, perhaps I am missing something.