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

Re: [PATCH] Fixed two bugs in git-cvsimport-script.

From
David Kågedal <davidk@lysator.liu.se>
Date
Aug 17, 2005, 10:07 UTC
Message-ID
<u5t64u427x7.fsf@lysator.liu.se>
In-Reply-To
<7v3bp829zj.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> writes:
Show 9 quoted lines
>> Apparently, my mail was encoded as QP, which is not very popular
>> around here.  But it seems that the diff part was decoded properly
>> before applying.  Was that done manually?
>
> Yes, the patch had some context conflicts with some other patch
> so the patch application was done by hand, and I did a quick and
> dirty cut & paste of the commit message from "cat mbox" output.
>
> I will probably drop future patches encoded in QP.

Ok, but do you have an answer to my real question? What is the character encoding for commit objects in your git repository?

It is obviously one that is compatible with ASCII, which probably leaves you with the alternatives ASCII, Latin1, and UTF-8. And plain ASCII obviously doesn't work very well for me.

-- 
David Kågedal
Previous: David Kågedal
Message 6 of 6 in “Fixed two bugs in git-cvsimport-script.”
  1. Fixed two bugs in git-cvsimport-script.David Kågedal, Aug 15, 2005
  2. David KågedalAug 17, 2005
  3. Junio C HamanoAug 17, 2005
  4. Junio C HamanoAug 17, 2005
  5. David KågedalAug 17, 2005
  6. David KågedalAug 17, 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.