From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] commit: reject invalid UTF-8 codepoints
Date: Thu, 4 Jul 2013 00:17:24 +0000 [thread overview]
Message-ID: <20130704001724.GQ862789@vauxhall.crustytoothpaste.net> (raw)
In-Reply-To: <7v7ghcl50r.fsf@alter.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
On Sat, Jun 29, 2013 at 07:13:40PM -0700, Junio C Hamano wrote:
> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
> > diff --git a/t/t3900/UTF-8-invalid.txt b/t/t3900/UTF-8-invalid.txt
> > new file mode 100644
> > index 0000000..343684d
> > --- /dev/null
> > +++ b/t/t3900/UTF-8-invalid.txt
> > @@ -0,0 +1,3 @@
> > +Commit message
> > +
> > +Invalid surrogate:???
>
> I suspect that I did not receive what you intended to send. Do you
> want to send this part as a binary patch perhaps?
git format-patch --binary seems to produce the exact same output as
without the --binary option. Is there a different way I should be
selecting the binary option?
--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-04 0:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 17:40 [PATCH 1/2] commit: reject invalid UTF-8 codepoints brian m. carlson
2013-06-30 2:13 ` Junio C Hamano
2013-06-30 2:29 ` brian m. carlson
2013-06-30 19:29 ` Junio C Hamano
2013-07-04 0:17 ` brian m. carlson [this message]
2013-07-04 0:47 ` Junio C Hamano
2013-07-01 7:12 ` Peter Krefting
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130704001724.GQ862789@vauxhall.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).