Yasushi SHOJI <yashi@xxxxxxxxxxxxxxxxx> writes: >> > sorry about my stupid english. What I meant was that because commi= > t >> > log doesn't say _why_ it changed to here-doc, I couldn't be sure it >> > was ok to overwrite the change introduced by the commit 59b9f61a3. >> > >> > IOW, I was tring to ask, "is it ok to revert back to print?" >>=20 >> Sure. Can I forge your Sign-off? > > =46rom 127a6abaf23991394b3b2c5455c2522f9da1e8ac Mon Sep 17 00:00:00 200= > 1 > =46rom: Yasushi SHOJI <yashi@xxxxxxxxxxxxxxxxxxxxx> > Date: Tue, 29 Jan 2008 20:48:33 +0900 > Subject: [PATCH] gitweb: Convert generated contents to utf8 in commitdi= > ff_plain > MIME-Version: 1.0 > Content-Type: text/plain; charset=3Dutf-8 > Content-Transfer-Encoding: 8bit Please don't do this. MIME headers do not belong to the body of the message. > > If the commit message, or commit author contains non-ascii, it must be > converted from Perl internal representation to utf-8, to follow what > got declared in HTTP header. Use to_utf8() to do the conversion. > > This necessarily replaces here-doc with "print" statements. > > Signed-off-by: Yasushi SHOJI <yashi@xxxxxxxxxxxxxxxxx> > Acked-by: =C4=B0smail D=C3=B6nmez <ismail@xxxxxxxxxxxxx> > Acked-by: Jakub Narebski <jnareb@xxxxxxxxx> Will try to apply by hand; if you do not hear from me about this patch again, no need for resend. Thanks. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
