From: Tor Arvid Lund <torarvid@gmail.com>
To: Dmitry Smirnov <divis1969@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: P4 Sync problem
Date: Wed, 11 Nov 2009 09:43:42 +0100 [thread overview]
Message-ID: <1a6be5fa0911110043i63b5c032s7924f9f1cdfe32ee@mail.gmail.com> (raw)
In-Reply-To: <loom.20091110T145046-137@post.gmane.org>
On Tue, Nov 10, 2009 at 2:56 PM, Dmitry Smirnov <divis1969@gmail.com> wrote:
> Hi,
>
> I'm trying to import Perfoce client into Git repository.
> I had configured git-p4.clent=MYCLIENT and git-p4.useclientspec=true.
>
> When runnign git p4 sync --verbose I got the follwing:
>
> c:\p4\views\Git\p4client>git p4 sync --verbose
<snip>
> Traceback (most recent call last):
> File "/usr/sbin/git-core//git-p4", line 1929, in ?
> main()
> File "/usr/sbin/git-core//git-p4", line 1924, in main
> if not cmd.run(args):
> File "/usr/sbin/git-core//git-p4", line 1676, in run
> changes = p4ChangesForPaths(self.depotPaths, self.changeRange)
> File "/usr/sbin/git-core//git-p4", line 442, in p4ChangesForPaths
> assert depotPaths
> AssertionError
Hi. So - I think the problem is that git-p4 doesn't understand what it
is you want to sync. The git-p4.useclientspec flag was created for the
purpose where your perforce depot may look like this:
//depot/project1
//depot/project1/source_code
//depot/project1/documentation
//depot/project1/some_large_collection_of_binaries
Then - if I set up my client spec like:
//depot/...
-//depot/project1/some_large_collection_of_binaries
... and do
git p4 sync //depot/project1@all
... it should get all project1 files except the
"some_large_collection_of_binaries" subdirectory (provided that you
have set the git-p4.client and git-p4.useclientspec).
-Tor Arvid-
next prev parent reply other threads:[~2009-11-11 8:43 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 [this message]
2009-11-11 9:43 ` Dmitry Smirnov
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=1a6be5fa0911110043i63b5c032s7924f9f1cdfe32ee@mail.gmail.com \
--to=torarvid@gmail.com \
--cc=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).