git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/2] Fix misaligned output of git repo structure

From
Jiang Xin <worldhello.net@gmail.com>
Date
Nov 14, 2025, 09:52 UTC
Message-ID
<CANYiYbGyGKy=S6a3NJFyrv-bOZos+BXdR=nPXDT3W_dGxeiNPA@mail.gmail.com>
In-Reply-To
<8cb5d668-783f-4400-89b4-35054a6cbea0@app.fastmail.com>

On Fri, Nov 14, 2025 at 3:41 PM Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com> wrote:

Show 14 quoted lines
>
> On Fri, Nov 14, 2025, at 06:52, Jiang Xin wrote:
> > While localizing Git 2.52.0, I noticed that the output table from git
> > repo structure becomes misaligned when displaying UTF-8 characters. For
> > example:
> >
> >[snip]
> >
> > BTW, I used two AI coding tools (Claude Code and Gemini-CLI) to generate
> > the commits, and added the "Co-developed-by" trailers in the commit
> > messages by using one of my opensource project:
>
> Is `Co-developed-by` supposed to have a different meaning than the more
> common `Co-authored-by`?
This is a very good question.
**Background**

At Alibaba Cloud, our development team uses a variety of AI coding tools, including Cursor, Claude Code, Gemini-CLI, Lingma, and Qoder, etc. To measure adoption—specifically, how many developers are using AI coding tools and how much code is AI-generated—we needed a unified tracking mechanism compatible with all these tools. I chose to implement a git commit-msg hook that automatically detects the AI coding tool responsible for a commit based on environment variables at commit time.

**Why choose the Co-developed-by trailer for AI developer?**

Git repositories already use the Co-authored-by trailer to credit human collaborators. Since any human developer, including co-authors, may use AI coding tools to assist their work, introducing a distinct trailer like Co-developed-by allows us to clearly differentiate between human contributors and the AI tools they used. For example, the following commit trailers indicate two human engineers and the respective AI coding tools they employed:

    Co-developed-by: Cursor <noreply@cursor.com>
    Co-authored-by: Real Person <real.person@example.com>
    Co-developed-by: Gemini <noreply@developers.google.com>
    Signed-off-by: Me <me@example.com>

I noticed that Sasha Levin (NVIDIA) previously proposed adopting the Co-developed-by trailer for the Linux kernel as well.

 - https://ostechnix.com/linux-kernel-ai-coding-assistants-rules-proposal/

-- Jiang Xin

Previous: Kristoffer HaugsbakkNext: Junio C Hamano
Message 14 of 22 in “Fix misaligned output of git repo structure”
  1. 0/2 Fix misaligned output of git repo structureJiang Xin, Nov 14, 2025
  2. 1/2 t/unit-tests: add UTF-8 width tests for CJK charsJiang Xin, Nov 14, 2025
  3. Junio C HamanoNov 14, 2025
  4. Jiang XinNov 15, 2025
  5. 2/2 builtin/repo: fix table alignment for UTF-8 charactersJiang Xin, Nov 14, 2025
  6. Justin ToblerNov 14, 2025
  7. Jiang XinNov 15, 2025
  8. Junio C HamanoNov 14, 2025
  9. Jiang XinNov 15, 2025
  10. Junio C HamanoNov 15, 2025
  11. Jiang XinNov 16, 2025
  12. Junio C HamanoNov 16, 2025
  13. Kristoffer HaugsbakkNov 14, 2025
  14. Jiang XinNov 14, 2025
  15. Junio C HamanoNov 14, 2025
  16. Jiang XinNov 15, 2025
  17. Junio C HamanoNov 14, 2025
  18. 0/2 Fix misaligned output of git repo structureJiang Xin, Nov 15, 2025
  19. 1/2 t/unit-tests: add UTF-8 width tests for CJK charsJiang Xin, Nov 15, 2025
  20. 2/2 builtin/repo: fix table alignment for UTF-8 charactersJiang Xin, Nov 15, 2025
  21. Phillip WoodNov 15, 2025
  22. Junio C HamanoNov 15, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.