From: Junio C Hamano <gitster@pobox.com>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v6] git-p4: Obey core.ignorecase when using P4 client specs.
Date: Wed, 26 Aug 2015 14:48:18 -0700 [thread overview]
Message-ID: <xmqqsi75202l.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <4CB47914-F04C-4E88-8D73-E00AFEFEF727@gmail.com> (Lars Schneider's message of "Wed, 26 Aug 2015 23:25:47 +0200")
Lars Schneider <larsxschneider@gmail.com> writes:
> On 26 Aug 2015, at 22:05, Junio C Hamano <gitster@pobox.com> wrote:
>
>> larsxschneider@gmail.com writes:
>>
>>> From: Lars Schneider <larsxschneider@gmail.com>
>>>
>>> We run P4 servers on Linux and P4 clients on Windows. For an unknown
>>> reason the file path for a number of files in P4 does not match the
>>> directory path with respect to case sensitivity.
>>
>> Thanks, but is this still "For an unknown reason", or during the
>> course of debugging you found the root cause, which is what led to
>> this fix?
> We are migrating away from P4 and therefore I haven’t debugged the
> root cause. The source of this problem is 100% P4 related. No Git
> involvement at all. Maybe I just remove this paragraph?
Perhaps. If it is irrelevant how the P4 depot ended up recording
the paths in mixed cases, then we can just say that as a prerequiste
condition to trigger the problem.
Perhaps rephrase the entire thing like this?
Perforce depot may record paths in mixed cases, e.g. "p4 files" may
show that there are these two paths:
//depot/path/to/file1
//depot/pATH/to/file2
and with "p4" or "p4v", these end up in the same directory, e.g.
//depot/path/to/file1
//depot/path/to/file2
which is the desired outcome on case insensitive systems.
If git-p4 is used with client spec "//depot/path/...", however, then
all files not matching the case in the client spec are ignored (in
the example above "//depot/pATH/to/file2").
Fix this by downcasing the depot_path when core.ignorcase is set to
true.
Thanks.
prev parent reply other threads:[~2015-08-26 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 16:08 [PATCH v6] git-p4: Obey core.ignorecase when using P4 client specs larsxschneider
2015-08-26 20:05 ` Junio C Hamano
2015-08-26 21:25 ` Lars Schneider
2015-08-26 21:48 ` 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=xmqqsi75202l.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=larsxschneider@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.