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

Re: [egit-dev] Re: jgit problems for file paths with non-ASCII characters

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Nov 26, 2009, 14:47 UTC
Message-ID
<alpine.DEB.1.00.0911261546350.7500@intel-tinevez-2-302>
In-Reply-To
<4B0E7DF5.9040007@syntevo.com>
Hi,
On Thu, 26 Nov 2009, Thomas Singer wrote:
Show 10 quoted lines
> [someone said, Thomas did not say who]
>
> > But as you said, this still doesn't make the Apple normal form any 
> > easier.  Though if we know we are on such a strange filesystem we 
> > might be able to assume the paths in the repository are equally 
> > damaged.  Or not.
> 
> Well, if the git-core folks could standardize on, e.g., composed UTF-8 
> (rather then just UTF-8), for storing file names in the repository, then 
> everything should be clear, isn't it?
You mean we should do the same thing as Apple with HFS?  Are you serious?

Ciao, Dscho

Previous: Thomas SingerNext: Thomas Singer
Message 5 of 10 in “jgit problems for file paths with non-ASCII characters”
  1. Marc StrapetzNov 25, 2009
  2. Robin RosenbergNov 25, 2009
  3. Shawn O. PearceNov 26, 2009
  4. Thomas SingerNov 26, 2009
  5. Johannes SchindelinNov 26, 2009
  6. Thomas SingerNov 26, 2009
  7. Shawn O. PearceNov 26, 2009
  8. Robin RosenbergNov 26, 2009
  9. Marc StrapetzNov 26, 2009
  10. Shawn O. PearceNov 26, 2009

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.