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

Re: [PATCH] [RFC] Design for pathname encoding gitattribute [RESEND]

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 22, 2008, 10:36 UTC
Message-ID
<7vprvuqh94.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<4795BE07.4040500@catalyst.net.nz>
Sam Vilain <sam.vilain@catalyst.net.nz> writes:
> On the chicken and egg thing, ...
> ...  I do agree with Dscho's point that mixing encodings in a
> repository is not necessarily a use case worth catering for.

Are you talking about "repository" as in "a specific clone", or "a project that can be cloned by many people and checked out to suit cloner's needs"? I definitely agree that mixing encodings in a project (i.e. "paths in tree objects") does not make any sense _if_ clones of the projects _may_ want to check things out in different pathname encodings from each other. And if all clones would want to check things out the same way, it does not really matter what encoding the paths in tree objects are.

I am not absolutely sure if you are talking about mixing encodings depending on parts of the tree in a specific clone (my earlier "Documentação/ja/ お読み下さい" example). I would certainly say it would be a very low priority for us to support such usage, as I imagine that multi-language trees would most likely be checked out in UTF-8 everywhere, but it _might_ be something people may find real need for.

Previous: Sam VilainNext: Sam Vilain
Message 10 of 11 in “[RFC] Design for pathname encoding gitattribute [RESEND]”
  1. [RFC] Design for pathname encoding gitattribute [RESEND]Sam Vilain, Jan 22, 2008
  2. Johannes SchindelinJan 22, 2008
  3. Junio C HamanoJan 22, 2008
  4. Junio C HamanoJan 22, 2008
  5. Junio C HamanoJan 22, 2008
  6. Mark JunkerJan 22, 2008
  7. Junio C HamanoJan 22, 2008
  8. Rafael Garcia-SuarezJan 22, 2008
  9. Sam VilainJan 22, 2008
  10. Junio C HamanoJan 22, 2008
  11. Sam VilainJan 22, 2008

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.