Re: [mpls-linux-devel] linux-kernel-2.6.14

[James R. L. <jl...@mi...>]

On Fri, Dec 02, 2005 at 09:05:50AM -0500, Bob Beers wrote:
<snip>
> BTW, is there a shortcut for 'p4 sync'?  When I do that, it gets
> _everything_ again,
>  doesn't seem to get just changed files -- (takes a _lo-o-o-o-ong_ time).

Your client view has a great impact on this.

What I do is have multiple clients each with a very specific view.
That way when sync'ing a client p4 only has to consider a small number
of files.  Also if you've been syncing recently there have been large
changes in the tree, merging that latest linux rev to all sorts of
branches.

BTW you can see all of the clients by doing a p4 clients (note 's' at the e=
nd).
Do 'p4 clients | grep jleu' and you'll see how many clients I have created.
Doing a 'p4 client -o <client-name>' and you can see what the details for
that client are.  For example doing a:

p4 client -o jleu:mpls-kernel-3

shows the details of my HOL mpls-kernel tree, and show the view I'm using:

        //depot/mpls-kernel-1.1/... //jleu:mpls-kernel-3/...

Which maps just the mpls-kernel-1.1 directory to my client.  If you
didn't modify your view, then your view looks like:

        //depot/... //jleu:mpls-kernel-3/...

Which means every directory in the dev tree is mapped into your client ...
which is a bad idea :-)

I see you have a client (actually 3, but they all look like they resuse
the same directory).  If I were you I would move all of the views execpt
for the mpls-kernel-1.1 to a new client.  Leave the mpls-kernel-1.1 line
so you don't have to re-sync it.  My guess is that the size of the
mpls-kernel-1.1 directory is what is making it so slow, that and the fact
my p4 server lives off of a DSL line with an upstream of 400Kbps.

--=20
James R. Leu
jl...@mi...