From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Tamir Duberstein" <tamird@gmail.com>, git@vger.kernel.org
Cc: "René Scharfe" <l.s.r@web.de>, "Patrick Steinhardt" <ps@pks.im>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH] ls-files: filter pathspec before lstat
Date: Sun, 06 Sep 2026 14:30:50 +0200 [thread overview]
Message-ID: <63821ef1-1234-49d5-b359-8631764457e1@app.fastmail.com> (raw)
In-Reply-To: <8f3bab63-3b37-4492-a39e-95e610a15a07@app.fastmail.com>
On Sun, Jun 7, 2026, at 18:02, Kristoffer Haugsbakk wrote:
> On Sun, Jun 7, 2026, at 17:40, Tamir Duberstein wrote:
>>[snip]
>> Assisted-by: Codex gpt-5.5
>
> This is more of a Git for Windows trailer. The Git project doesn’t
> document its use.
>
> An aside here but these trailers attributing specific LLMs feels like
> etching “Peter was here” under some table. What benefit for the project
> does knowing that it was this version of Codex or Claude or something?
> A link to the prompt/conversation would provide provenance and show how
> the LLM was used. But three years from now, what information beyond the
> fact that an LLM was involved (any of them) does this offer?
>
> I can understand the benefit for the companies behind these LLMs to have
> these attributions in OSS projects.
>
> I have done the same thing in our company repo, crediting <LLM> for
> authoring or co-authoring or helping with a specific thing. Using a
> “people” trailer. But the intent was just to show how some LLM was
> involved. So I think I am going to switch to the following trailer for
> our company repo.
>
> LLM: Yes
>
>> [snip]
The Linux Kernel has since then simplified the mandatory attribution to
just “LLM”:
The requirement to identify specific models used in the Assisted-by tag
provides free advertising to proprietary software companies while adding
little or no useful information. Change the requirement to simply:
Assisted-by: LLM
to capture the fact that an LLM was used without tracking which one.
https://lore.kernel.org/workflows/87qzkuahlr.fsf@trenco.lwn.net/#t
See linux/816d9992 (coding-assistants: simplify attribution,
2026-07-01).
next prev parent reply other threads:[~2026-09-06 12:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 15:40 [PATCH] ls-files: filter pathspec before lstat Tamir Duberstein
2026-06-07 16:02 ` Kristoffer Haugsbakk
2026-06-07 16:07 ` Tamir Duberstein
2026-06-07 16:17 ` Kristoffer Haugsbakk
2026-06-07 18:24 ` Tamir Duberstein
2026-09-06 12:30 ` Kristoffer Haugsbakk [this message]
2026-06-08 13:06 ` Junio C Hamano
2026-06-08 19:15 ` Tamir Duberstein
2026-06-08 23:03 ` Jeff King
2026-06-08 23:25 ` Jeff King
2026-06-09 0:13 ` Tamir Duberstein
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=63821ef1-1234-49d5-b359-8631764457e1@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=l.s.r@web.de \
--cc=ps@pks.im \
--cc=tamird@gmail.com \
/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