From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Weijie Yuan <wy@wyuan.org>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Alexey Samsonov via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Alexey Samsonov <vonosmas@gmail.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH 0/3] treewide: migrate from legacy utime.h to utimensat
Date: Mon, 24 Aug 2026 22:25:27 +0200 [thread overview]
Message-ID: <aoyot_mI2uX8VL8c@ugly.lan> (raw)
In-Reply-To: <xmqqjypfqz9e.fsf@gitster.g>
On Mon, Aug 24, 2026 at 09:06:21AM -0700, Junio C Hamano wrote:
>By "sufficient due diligence", what I meant was that I trust Dscho
>well enough that he's done a similar analysis to make sure that he
>is copying from ourselves.
>
i think the salient point is that it is never reasonable to make that
assumption when an AI tool is used. some of the tools now reportedly
detect themselves when they are outright plagiarizing (and identifying
the tool in a trailer would actually give some assurance in that
regard), but if the tool fails or doesn't have the feature in the first
place, then all bets are off. Literally No-one (TM) will use multiple
code search engines to check whether the generated code doesn't contain
sufficiently large fragments that are (near-)verbatim copies from
incompatibly licensed code bases.
prev parent reply other threads:[~2026-08-24 20:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 14:23 [PATCH 0/3] treewide: migrate from legacy utime.h to utimensat Alexey Samsonov via GitGitGadget
2026-08-21 14:23 ` [PATCH 1/3] compat/posix: introduce utimensat(2) wrapper Alexey Samsonov via GitGitGadget
2026-08-21 14:23 ` [PATCH 2/3] treewide: use utimensat(2) instead of legacy utime(3p) Alexey Samsonov via GitGitGadget
2026-08-21 14:23 ` [PATCH 3/3] compat/posix: drop legacy <utime.h> header and shims Alexey Samsonov via GitGitGadget
2026-08-21 17:33 ` [PATCH 0/3] treewide: migrate from legacy utime.h to utimensat Junio C Hamano
2026-08-22 16:03 ` brian m. carlson
2026-08-22 17:59 ` Junio C Hamano
2026-08-22 21:15 ` brian m. carlson
2026-08-23 15:23 ` Junio C Hamano
2026-08-23 13:26 ` Weijie Yuan
2026-08-23 15:26 ` Junio C Hamano
2026-08-23 15:45 ` Weijie Yuan
2026-08-24 1:49 ` Junio C Hamano
2026-08-24 12:19 ` Weijie Yuan
2026-08-24 15:33 ` Weijie Yuan
2026-08-24 16:06 ` Junio C Hamano
2026-08-24 16:23 ` Junio C Hamano
2026-08-24 16:33 ` Weijie Yuan
2026-08-24 20:25 ` Oswald Buddenhagen [this message]
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=aoyot_mI2uX8VL8c@ugly.lan \
--to=oswald.buddenhagen@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=sandals@crustytoothpaste.net \
--cc=vonosmas@gmail.com \
--cc=wy@wyuan.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