From: Junio C Hamano <gitster@pobox.com>
To: Tor Arvid Lund <torarvid@gmail.com>
Cc: Pete Wyckoff <pw@padd.com>, Vitor Antunes <vitor.hda@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH v2 7/8] git-p4: decode p4 wildcard characters
Date: Thu, 24 Feb 2011 08:40:55 -0800 [thread overview]
Message-ID: <7voc612xns.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <AANLkTik=KWwszN9ETOh11btPvcPXCcoA=evT4Fgxt-Fm@mail.gmail.com> (Tor Arvid Lund's message of "Thu\, 24 Feb 2011 14\:54\:56 +0100")
Tor Arvid Lund <torarvid@gmail.com> writes:
> On Thu, Feb 24, 2011 at 1:12 PM, Pete Wyckoff <pw@padd.com> 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?
next prev parent reply other threads:[~2011-02-24 16:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 13:17 [PATCH v2 0/8] git-p4 fixes and enhancements Pete Wyckoff
2011-02-19 13:17 ` [PATCH v2 1/8] git-p4: test script Pete Wyckoff
2011-02-19 13:17 ` [PATCH v2 2/8] git-p4: fix key error for p4 problem Pete Wyckoff
2011-02-19 13:17 ` [PATCH v2 3/8] git-p4: add missing newline in initial import message Pete Wyckoff
2011-02-19 13:17 ` [PATCH v2 4/8] git-p4: accommodate new move/delete type in p4 Pete Wyckoff
2011-02-21 23:32 ` Junio C Hamano
2011-02-19 13:17 ` [PATCH v2 5/8] git-p4: reinterpret confusing p4 message Pete Wyckoff
2011-02-23 8:26 ` Tor Arvid Lund
2011-02-19 13:17 ` [PATCH v2 6/8] git-p4: better message for "git-p4 sync" when not cloned Pete Wyckoff
2011-02-19 13:18 ` [PATCH v2 7/8] git-p4: decode p4 wildcard characters Pete Wyckoff
2011-02-21 23:32 ` Junio C Hamano
2011-02-24 12:12 ` Pete Wyckoff
2011-02-24 13:54 ` Tor Arvid Lund
2011-02-24 16:40 ` Junio C Hamano [this message]
2011-02-27 21:16 ` Pete Wyckoff
2011-02-19 13:18 ` [PATCH v2 8/8] git-p4: support clone --bare Pete Wyckoff
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=7voc612xns.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pw@padd.com \
--cc=torarvid@gmail.com \
--cc=vitor.hda@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).