From: Junio C Hamano <gitster@pobox.com>
To: Steffen Prohaska <prohaska@zib.de>
Cc: git@vger.kernel.org, mitcht.git@gmail.com
Subject: Re: [PATCH] Add tests for filesystem challenges (case and unicode normalization)
Date: Mon, 25 Feb 2008 16:28:20 -0800 [thread overview]
Message-ID: <7vlk58ftnf.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <FBFBA30A-0D44-4A2A-A693-EFF79218FCEB@zib.de> (Steffen Prohaska's message of "Tue, 26 Feb 2008 00:34:56 +0100")
Steffen Prohaska <prohaska@zib.de> writes:
> This is a sensible way of handling this. It works for me,
> except for ...
> ...
> test_case (instead of test_camel).
Thanks for testing. Fixed.
prev parent reply other threads:[~2008-02-26 0:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 7:09 Add case-challenged file system tests Steffen Prohaska
2008-02-08 7:09 ` [PATCH] [WIP] git on MacOSX and files with decomposed utf-8 file names Steffen Prohaska
2008-02-08 18:02 ` Add case-challenged file system tests Junio C Hamano
2008-02-24 17:19 ` [PATCH] Add tests for filesystem challenges (case and unicode normalization) Steffen Prohaska
2008-02-25 20:44 ` Junio C Hamano
2008-02-25 23:34 ` Steffen Prohaska
2008-02-26 0:28 ` Junio C Hamano [this message]
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=7vlk58ftnf.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mitcht.git@gmail.com \
--cc=prohaska@zib.de \
/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;
as well as URLs for NNTP newsgroup(s).