From: Juergen Ruehle Date: Wed, 10 Jan 2007 18:33:21 GMT Subject: Re: [PATCH] Provide better feedback for the untracked only case in status output Message-ID: <17829.12657.814000.514351@lapjr.intranet.kiel.bmiag.de> In-Reply-To: <7v4pqzfhzd.fsf@assigned-by-dhcp.cox.net> Junio C Hamano writes: > Juergen Ruehle writes: > > > Juergen Ruehle writes: > > > [Corrupted patch deleted] > > > > Will try again when I know what happened. > > While you are at it, let me point out one thing that has been > annoying me for a while. > > * The message claims to be from git-send-email; > > * Content-Type and CTE are UTF-8 and QP (which is fine); > > * You have in-body From: line; this is not wrong per-se and I > understand why you would want one (your e-mail From: line > uses ASCII approximations "ue" and "ue" and you would want > the resulting commit to spell your name correctly). > > * However, this in-body From: line is _doubly_ QP encoded (what > you see above is your name, first RFC 2047 encoded and then > QP encoded). It shouldn't be. > > So, my questions are: > > (1) is this what git-send-email generates and sends out by > default? If so that means it is a bug in that program that > needs to be fixed. > > (2) if not, are you inserting the in-body From: by hand, > perhaps cut & paste from format-patch output, before > feeding git-send-email (which runs QP on it)? > > If the latter, please do not paste the RFC 2047 quoted form. > You can spell your name in raw UTF-8 on the in-body From: line > just like you did on your Signed-off-by: line. Yes, this is using git-send-email which sends the mail as 8bit encoded and provides the QP encoded From line. Unfortunately there seems to be a gateway in between that doesn't handle 8bit and QPs the mail again. Perhaps I need some other switches for format-patch and send-email to produce a better result? I'll take another look at the documentation before annoying you again.