From: Dmitry Smirnov <divis1969@gmail.com>
To: git@vger.kernel.org
Subject: Re: P4 Sync problem
Date: Wed, 11 Nov 2009 09:43:52 +0000 (UTC) [thread overview]
Message-ID: <loom.20091111T100646-406@post.gmane.org> (raw)
In-Reply-To: 1a6be5fa0911110043i63b5c032s7924f9f1cdfe32ee@mail.gmail.com
Tor Arvid Lund <torarvid <at> gmail.com> writes:
> Hi. So - I think the problem is that git-p4 doesn't understand what it
> is you want to sync.
I believe it will never understand that until self.depotPaths
will be initialized.
It looks like it is intitilized from argument list only (or from already saved
settings). See P4Sync.run().
But self.getClientSpec() which is called some time before, does not init neither
self.depotPaths nor args.
I had fixed this with the following code (new lines marked with +):
if self.useClientSpec or gitConfig("git-p4.useclientspec") == "true":
+ if self.verbose:
+ print "Get client spec"
self.getClientSpec()
+ if self.verbose:
+ print "Client Spec Dirs: %s" % self.clientSpecDirs
+ if len(args) == 0:
+ for item in self.clientSpecDirs:
+ k,v = item
+ args.append(k)
Unfortunately, this fails on another stage:
>git p4 sync --verbose
Reading pipe: git config git-p4.useclientspec
Get client spec
Reading pipe: git config git-p4.user
Reading pipe: git config git-p4.password
Reading pipe: git config git-p4.port
Reading pipe: git config git-p4.host
Reading pipe: git config git-p4.client
p4 -c MYCLIENT-G client -o
Opening pipe: p4 -c MYCLIENT-G client -o
Client Spec Dirs:[ <my paths here> ]
Doing initial import of <my paths here> from revision #head into
refs/remotes/p4/master
p4 -c MYCLIENT-G files <my paths here appended with ...#head >
Opening pipe: p4 -c MYCLIENT-G files <my paths here appended with ...#head >
p4 returned an error: //MYCLIENT/path/file.c/...#head> - file(s) not in client
view.
My client spec contains some line to the file:
-//depot/path/... //MYCLIENT/null/...
//depot/path/file.cs //MYCLIENT/path/file.cs
This means that I wish to sync only file.cs into my client and get rid of other
files in this directory.
BTW, note that file extension is truncated in the log
Dmitry
next prev parent reply other threads:[~2009-11-11 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 13:56 P4 Sync problem Dmitry Smirnov
2009-11-11 8:43 ` Tor Arvid Lund
2009-11-11 9:43 ` Dmitry Smirnov [this message]
2009-11-11 12:00 ` Tor Arvid Lund
2009-11-11 12:39 ` Dmitry Smirnov
2009-11-11 13:54 ` Tor Arvid Lund
2009-11-11 14:57 ` Dmitry Smirnov
2010-07-22 18:21 ` masonk
2009-11-15 13:00 ` 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=loom.20091111T100646-406@post.gmane.org \
--to=divis1969@gmail.com \
--cc=git@vger.kernel.org \
/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).