[p4] Re: p4d patch?
rich.ireland at idahotech.com
Sun Jan 25 13:22:49 PST 2004
Nevermind, I just found the info in the Release Notes. Note to
Perforce Staff, please update the *date* in the Release Notes when you
update the file...
> Bugs fixed since 2003.2/51929 (first release).
> #52835 **
> The Perforce server could incorrectly report a lack of
> available memory on the Mac OS X platform. (Bug #13198)
> #52747 **
> 'p4 files //... at labelname' or similar could return incomplete
> results if some of the files involved were from a remote depot.
> This has been fixed. (Bug #13162).
> #52650 **
> The @change,change syntax, where change was old, could
> be slower in 2003.2 than 2003.1. (This syntax is generated
> by p4win and other programs when integrating by change
> number.) This has been optimized to be as fast as the
> new @=change syntax. (Bug #13150).
> #52585 **
> After upgrading to 2003.2 some user passwords may not
> work anymore. This upgrade process has now been fixed.
> (Bug #13164)
> #52474 **
> Users without access could create (useless) entries for
> themselves in the users table, consuming a user license.
> They can no longer do so. This was new to 2003.2. (Bug
Rich Ireland wrote:
> I noticed today, just after upgrading to 2003.2, that there is a p4d
> patch announced on the Software Updates page:
> However, there are no details on just what this patch is for. Does
> anyone have any idea if this is a serious, 'must patch' thing or not?
Firmware Engineer - Perforce Advocate
Idaho Technology, Inc.
mailto:rich.ireland at idahotech.com
More information about the perforce-user