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

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

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

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:42:04

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.

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

From: David Kågedal <hidden>
Date: 2016-06-15 22:42:04

Junio C Hamano [off-list ref] writes:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help