From: "Torsten Bögershausen" <tboegi@web.de>
To: "Reuben Hawkins" <reubenhwk@gmail.com>,
"Torsten Bögershausen" <tboegi@web.de>
Cc: git@vger.kernel.org, Dmitry Potapov <dpotapov@gmail.com>
Subject: Re: [PATCH] fast-import.c: always honor the filename case
Date: Sun, 09 Feb 2014 21:34:26 +0100 [thread overview]
Message-ID: <52F7E652.4030102@web.de> (raw)
In-Reply-To: <CAD_8n+Thn3tNTYxLK49mDOGdLpWRCFUCJo9b76UbAjnCdqXsRQ@mail.gmail.com>
On 2014-02-06 12.24, Reuben Hawkins wrote:
[snipped away minor interesting stuff]
Reading the answers from Peff and Junio, I am convinced that the fast-import should
not look at core.ignorecase at all.
Agreed, but my patch 0001-fast-import.c-ignorecase-iff-... is working very well (for me anyway), and the ignore-case option may be useful to the git-p4 importer (which I guess is something that should be determined for sure).
If you want, you can turn this into a real patch and send it to the list.
I think Pete Wyckoff <pw@padd.com> is one of the experts about p4.
And the same is for fast-export fixes you have made: If you have the time,
convert it into a patch and send it to the list.
[]
> BTW, if you can, can you give me a quick overview of testing it git? I can run 'make tests' easy enough, but there seems to be a well defined framework of testing written in bash and c.. Is there a doc on that framework anywhere?
I'm not sure if there is a document, and yes, it's a nice framework.
You can have a look at t0050, it gives a good overview over the most important
feattures in the framework, I would say.
(And the shell scripts uses a subset of the POSIX shell, which means we avoid
bash-ism things like "[[ ]]" or "==")
/Torsten
next prev parent reply other threads:[~2014-02-09 20:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 13:13 [PATCH] fast-import.c: always honor the filename case Reuben Hawkins
2014-02-02 20:08 ` Torsten Bögershausen
[not found] ` <CAD_8n+RZACW0380co75gWSwVmCJdcH4COsySTF3BFCyKEumXNA@mail.gmail.com>
2014-02-03 20:21 ` Torsten Bögershausen
2014-02-04 0:14 ` Junio C Hamano
[not found] ` <CAD_8n+RuwQEXJRCOr+B_PqA7z6LkFdbcRZkiiVJsEhJ=+YjRDg@mail.gmail.com>
2014-02-05 21:19 ` Torsten Bögershausen
[not found] ` <CAD_8n+Thn3tNTYxLK49mDOGdLpWRCFUCJo9b76UbAjnCdqXsRQ@mail.gmail.com>
2014-02-09 20:34 ` Torsten Bögershausen [this message]
[not found] ` <CAD_8n+ToUDbXrVuru7GV7toYKHXuQb8vL3B_-sfzQdXZFqzD2A@mail.gmail.com>
2014-02-11 17:29 ` Torsten Bögershausen
2014-02-02 23:00 ` Jeff King
2014-02-03 17:21 ` Junio C Hamano
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=52F7E652.4030102@web.de \
--to=tboegi@web.de \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=reubenhwk@gmail.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.
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).