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

Re: P4 Sync problem

From
DSDmitry Smirnov <divis1969@gmail.com>
Date
Nov 11, 2009, 12:39 UTC
Message-ID
<loom.20091111T131837-901@post.gmane.org>
In-Reply-To
<1a6be5fa0911110400l1fe931afmbb53ceba8704e029@mail.gmail.com>
Tor Arvid Lund <torarvid <at> gmail.com> writes:
Show 10 quoted lines
> Well, I see what you're trying to do, but I would not want to see that
> patch in the official script, because some (most?) people (myself, at
> least) use git-p4 to clone single projects out of a perforce depot
> that may contain many projects. I do this myself by doing:
> 
> git p4 clone //depot/path/to/projectX <at> all
> 
> I usually use one clientspec in perforce, and I do not want to change
> that... With your patch, I would be in trouble since my clientspec
> contains "//depot/..." (followed by a lot of lines starting with '-')

Well, does this mean that if you try to sync the client in perforce (visual or command line), you will sync all the projects?

In that case, git p4 will require significant effort to satisfy both of us :-) Unfortunatly, it seems I'm in minory group of git-p4 users...

i would propose to use both command-line arguments and a client spec 
to create a correct filter of what should be synced/cloned.
BTW, it looks this script does not honor neither the order of paths 
in the spec (which can be important) nor mapping of the files to a local tree.
 
> If you want to fix it, you might want to rename clientSpecDirs to
> clientSpecEntries or something like that.
For now, I just commented out two lines in the run() procedure:
            #if not p.endswith("/"):
            #    p += "/"
> Btw... Am I understanding correctly what it is you wish to accomplish?
> I'm guessing that you have a perforce server with a client spec set
> up, and you want to sync everything on the entire server according to
> that client spec?

yes. Client spec completely defines the project layout for me. It contains paths to some components that are mapped to the client working tree. Just if your CS contain

//depot/path/to/projectX/... //CLIENT/...
Previous: Tor Arvid LundNext: Tor Arvid Lund
Message 5 of 9 in “P4 Sync problem”
  1. Dmitry SmirnovNov 10, 2009
  2. Tor Arvid LundNov 11, 2009
  3. Dmitry SmirnovNov 11, 2009
  4. Tor Arvid LundNov 11, 2009
  5. Dmitry SmirnovNov 11, 2009
  6. Tor Arvid LundNov 11, 2009
  7. Dmitry SmirnovNov 11, 2009
  8. masonkJul 22, 2010
  9. Pete WyckoffNov 15, 2009

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.