From: Tim Tassonis <stuff@decentral.ch>
To: git@vger.kernel.org
Subject: Release Notes wrongly identify git as a self-learning program
Date: Fri, 2 Jun 2023 14:08:03 +0200 [thread overview]
Message-ID: <1201c202-e046-01a3-df87-d959f0611725@decentral.ch> (raw)
Hi all
When checking the release notes of Git v2.4, I stumbled upon various
hilariously stupid entries like:
* "git format-patch" learned to write...
* "git clone" from an empty repository learned to propagate ...
* "git send-email" learned to giv
and even:
* "git mergetool" and "git difftool" learns a new...
* The credential subsystem learns
I can maybe live with:
* "git push" has been taught
* A few subcommands have been taught
Is this some sort of joke, or AI/chat-gpt bandwagonin?
To my knowledge, git 2.41 still is a piece of software written and
enhanced by human beings and neither is taught something, let alone even
"learned" or is "learning" something.
Why on earth is git now being described as some sort of sentient,
self-optimizing being?
Are technical git Release Notes now being written some kind of marketing
people?
Bye
Tim
next reply other threads:[~2023-06-02 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 12:08 Tim Tassonis [this message]
2023-06-02 12:56 ` Release Notes wrongly identify git as a self-learning program Kristoffer Haugsbakk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1201c202-e046-01a3-df87-d959f0611725@decentral.ch \
--to=stuff@decentral.ch \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).