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

Re: gitweb on kernel.org and UTF-8

From
RARyan Anderson <ryan@michonline.com>
Date
Nov 24, 2005, 05:01 UTC
Message-ID
<20051124050104.GC16995@mythryan2.michonline.com>
In-Reply-To
<7vfypm20eh.fsf@assigned-by-dhcp.cox.net>
On Wed, Nov 23, 2005 at 07:24:38PM -0800, Junio C Hamano wrote:
Show 12 quoted lines
> 
> How about doing something like this?
> 
> 	[i18n]
>         	commitEncoding = utf8
> 		blobEncoding = utf8
> 
> to mean:
> 
> 	If you _have_ to make an assumption on an encoding
> 	commit and blob objects are in, utf8 is your best bet
> 	(but mistakes can happen, and some blobs can be binary).

The rest of the options help clarify this, but can you make these options 'assumeCommitEncoding' and 'assumeBlobEncoding' to make it clear that these are *assumptions* and not actually controlling what gets written?

-- 
Ryan Anderson
  sometimes Pug Majere
Previous: Junio C HamanoNext: Junio C Hamano
Message 6 of 7 in “gitweb on kernel.org and UTF-8”
  1. Junio C HamanoNov 23, 2005
  2. H. Peter AnvinNov 23, 2005
  3. Kay SieversNov 23, 2005
  4. H. Peter AnvinNov 23, 2005
  5. Junio C HamanoNov 24, 2005
  6. Ryan AndersonNov 24, 2005
  7. Junio C HamanoNov 24, 2005

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.