[p4] The story of the null delta.

[Oren Shemesh (oshemesh)]

Yes there is, you can over-ride the client options with a flag to the
submit command.

Details are in the excellent documentation.

Oren. 

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of David Weintraub
Sent: Tuesday, March 27, 2007 8:55 PM
To: Shawn Hladky
Cc: Perforce Users; Peter Prymmer
Subject: Re: [p4] The story of the null delta.

On 3/26/07, Shawn Hladky <p4shawn at gmail.com> wrote:
> Server version 2006.2 gives you a variety of options you can set on
your
> client that will determine what happens to unchanged files.

That's nice to see there's now an option. However, using it probably
does slow down the submit process since Perforce now has to verify
each file in the change list. The delay is probably not too bad for
short changelists that consist mostly of source files, but long
changelists with lots of binaries might take a while.

I guess it is still quicker than CVS or Subversion. Both of which have
to go through the whole source tree in order to find all the files
that have changed.

I have 2006.1 running, so I didn't have this new feature. Is there
anything on the Submit command itself? That way, I can override the
behavior of the client when I want to without having to modify the
client.

--
David Weintraub
qazwart at gmail.com
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user