From: "David Kågedal" <davidk@lysator.liu.se>
To: git@vger.kernel.org
Subject: Re: [PATCH] Fixed two bugs in git-cvsimport-script.
Date: Wed, 17 Aug 2005 13:22:03 +0200 [thread overview]
Message-ID: <u5t1x4s24h0.fsf@lysator.liu.se> (raw)
In-Reply-To: 7vacjgyj94.fsf@assigned-by-dhcp.cox.net
Junio C Hamano <junkio@cox.net> writes:
> Junio C Hamano <junkio@cox.net> writes:
>
>> 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.
>
> This was totally inappropriate; sorry, but I was in a bad mood.
>
> A more serious response.
>
> - I personally consider commit message encoding a per project
> issue (so is blob contents encoding).
Agreed. And your response is probably good enough for now. I also
think that having UTF-8 as the standard convention is the way to go.
--
David Kågedal
next prev parent reply other threads:[~2005-08-17 11:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 18:18 [PATCH] Fixed two bugs in git-cvsimport-script David Kågedal
2005-08-17 8:07 ` David Kågedal
2005-08-17 9:22 ` Junio C Hamano
2005-08-17 10:01 ` Junio C Hamano
2005-08-17 11:22 ` David Kågedal [this message]
2005-08-17 10:07 ` David Kågedal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u5t1x4s24h0.fsf@lysator.liu.se \
--to=davidk@lysator.liu.se \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox