git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Vitor Antunes <vitor.hda@gmail.com>
Date
Apr 20, 2015, 22:25 UTC
Message-ID
<48EB5BF2-166D-45F5-9573-0C9E16CAC2B9@gmail.com>
In-Reply-To
<xmqqtwwbmk16.fsf@gitster.dls.corp.google.com>
On April 20, 2015 6:43:49 AM GMT+01:00, Junio C Hamano <gitster@pobox.com> wrote:
Show 9 quoted lines
>Vitor Antunes <vitor.hda@gmail.com> 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 "use".  Is it "user client view" or something (I am not
>familiar with p4 lingo), or perhaps "use of client view"?
I meant "spec" instead of "view". As in - -use-client-spec.

In perforce you need to configure your workspace using a client specification. One of the configured values is the client view, which maps files/folders in the server to locations in your local workspace. What I'm trying to fix with these patches is the ability of git-p4 to process the client view definition through the use of "p4 where" to determine the correct location of the local files, such that it is able to apply the necessary patches for submission to the perforce server.

While thinking about client views I completely forgot that the git-p4 argument that enables thos feature uses "spec" and not "view".

Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 7 in “git-p4: improve client path detection with branches used”
  1. 0/2 git-p4: improve client path detection with branches usedVitor Antunes, Apr 19, 2015
  2. 1/2 t9801: check git-p4's branch detection and client view togetherVitor Antunes, Apr 19, 2015
  3. Junio C HamanoApr 20, 2015
  4. Vitor AntunesApr 20, 2015
  5. Junio C HamanoApr 20, 2015
  6. Vitor AntunesApr 21, 2015
  7. 2/2 git-p4: improve client path detection when branches are usedVitor Antunes, Apr 19, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.