From: Junio C Hamano Date: Thu, 24 Feb 2011 16:40:55 GMT Subject: Re: [PATCH v2 7/8] git-p4: decode p4 wildcard characters Message-ID: <7voc612xns.fsf@alter.siamese.dyndns.org> In-Reply-To: Tor Arvid Lund writes: > On Thu, Feb 24, 2011 at 1:12 PM, Pete Wyckoff wrote: > ... > Yeah, I was thinking... what happens now if we do: > > 1) Create "my*file" in linux, and submit. > 2) git-p4 sync from windows, and get my%2Afile on windows. > 3) modify my%2Afile and do git commit. > 4) git-p4 submit > > I haven't had time to test right now, but maybe p4 will not recognise > my%2Afile (or try to check it in as my%252Afile (replacing the '%' > character) or something like that? (Or maybe I just haven't had enough > coffee today :-/ ) This shares the same issue as "checking files out on case insensitive filesystems" topic in the other thread. "my*file" may not be usable by the project when renamed to "my%2Afile", so "git-p4 sync" may want to warn the user about the path when this happens. And you need to reverse this quoting upon "git-p4 submit". Does that happen already?