Re: [PATCH v2] git p4: implement view spec wildcards with p4 where

2013-09-05 Thread kazuki saitoh
2013/9/4 Junio C Hamano gits...@pobox.com: kazuki saitoh ksaitoh...@gmail.com writes: Currently, git p4 does not support many of the view wildcards, such as * and %%n. It only knows the common ... mapping, and exclusions. Redo the entire wildcard code around the idea of directly querying

[PATCH v2] git p4: implement view spec wildcards with p4 where

2013-08-30 Thread kazuki saitoh
as args and use the client mapping to decide where the file goes in git. This simplifies a lot of code, and adds support for all wildcards supported by p4. Downside is that there is probably a 20%-ish slowdown with this approach. [pw: redo code and tests] Signed-off-by: Kazuki Saitoh ksaitoh

Re: [PATCH v2] git-p4: Ask p4 to interpret View setting

2013-08-26 Thread kazuki saitoh
Do you have an updated patch? Want to take some time to clean up and resubmit the entire series? The batching should be incorporated with the last 2/2 that I sent out. I don't have other update. I'm satisfied because able to want to do and it became better than my original modification

[PATCH v2] git-p4: Ask p4 to interpret View setting

2013-08-06 Thread kazuki saitoh
In Perforce, View setting of p4 client can describe -//depot/project/files/*.xls //client/project/files/*.xls to exclude Excel files. But git p4 --use-client-spec cannot support '*'. In git-p4.py, map_in_client method analyzes View setting and return client file path. So I modify the method to

Re: [PATCH] git-p4: use p4 fstat to interpret View setting

2013-08-04 Thread kazuki saitoh
Hi, Pete Thank you reply. Your theory is: there is a client spec, and p4 knows how to interpret these things, so instead of figuring out and implementing the algorithms for %% and * and ... in git-p4, just ask p4 directly. That's right. It is simple way to get my purpose unless break