Re: [PATCH V2 1/2] t9801: check git-p4's branch detection and client view together

On April 20, 2015 11:45:15 PM GMT+01:00, Junio C Hamano wrote: >Vitor Antunes writes: > >> On April 20, 2015 6:43:49 AM GMT+01:00, Junio C Hamano > wrote: >>>Vitor Antunes writes: >>> Add failing scenario where branch detection is enabled together >with use client view. In this specif

Re: [PATCH V2 1/2] t9801: check git-p4's branch detection and client view together

Vitor Antunes writes: > On April 20, 2015 6:43:49 AM GMT+01:00, Junio C Hamano > wrote: >>Vitor Antunes writes: >> >>> Add failing scenario where branch detection is enabled together with >>> use client view. In this specific scenario git-p4 will break when the >>> perforce client view removes

Re: [PATCH V2 1/2] t9801: check git-p4's branch detection and client view together

On April 20, 2015 6:43:49 AM GMT+01:00, Junio C Hamano wrote: >Vitor Antunes writes: > >> Add failing scenario where branch detection is enabled together with >> use client view. In this specific scenario git-p4 will break when the >> perforce client view removes part of the depot path. > >I som

Re: [PATCH V2 1/2] t9801: check git-p4's branch detection and client view together

Vitor Antunes writes: > Add failing scenario where branch detection is enabled together with > use client view. In this specific scenario git-p4 will break when the > perforce client view removes part of the depot path. I somehow cannot parse "together with use client view", especially the word

[PATCH V2 1/2] t9801: check git-p4's branch detection and client view together

Add failing scenario where branch detection is enabled together with use client view. In this specific scenario git-p4 will break when the perforce client view removes part of the depot path. The test case also includes an extra sub-file mapping to enforce robustness check on git-p4 implementation