non port: devel/perforce/distinfo.freebsd60x86_64 |
SVNWeb
|
Number of commits found: 10 |
Thu, 20 May 2010
|
[ 23:34 rene ] (Only the first 10 of 11 ports in this commit are shown above. )
Remove old devel/perforce
The server parts are now in devel/p4d, devel/p4p, devel/p4ftpd, and devel/p4web
PR: ports/145824
Submitted by: gordon
Approved by: tabthorpe (mentor)
|
Tue, 24 Mar 2009
|
[ 08:32 lth ]
Updated p4d. Bugs fixed:
#189734 **
The new tcp buffer calculation could cause a deadlock in
client/server communications. This problem was only detected
on configurations involving Solaris or Linux. Due to the
complications of platform specific tcp implementations the
algorithm has been reworked to make allowances for certain
eccentricities. (Bug #32494).
#188676 *
'p4 resolve' using the automatic option could crash the client
application when running on windows. This would only happen
if the 'theirs' file had been locked by another windows
application e.g. microsoft word. (Bug #32384)
Updated p4web. Bugs fixed:
#190006
Always offer browse depot selection in multiuser mode. (Bug #32704)
Complete release notes at:
http://www.perforce.com/perforce/doc.082/user/relnotes.txt
http://www.perforce.com/perforce/doc.082/user/p4webnotes.html
|
Wed, 25 Feb 2009
|
[ 07:26 lth ]
Updated p4web. Bugs fixed:
#186658
Fix problem with line numbers being skipped when viewing a file.
(Bug #031832)
#185786
P4Web no longer requires a client in browse only mode. (Bug #032227)
Complete release notes for p4web at:
http://www.perforce.com/perforce/doc.current/user/p4webnotes.html
|
Sun, 22 Feb 2009
|
[ 13:58 lth ]
Bugs fixed (from release notes):
#188676 *
'p4 resolve' using the automatic option could crash the client
application when running on windows. This would only happen
if the 'theirs' file had been locked by another windows
application e.g. microsoft word. (Bug #32384)
#188603 **
A user with a complicated view map could crash the server
by creating a spec using '-i' or editing a spec to use
a name which contains '%%<somenumber>'. This has
been fixed. (Bug #31933)
Noted by: pointyhat via pav
|
Fri, 23 Jan 2009
|
[ 16:21 lth ]
Bugs fixed (from release notes):
#179182 **
'p4 sync -p' via the proxy did not transfer files which
were not in the proxy's cache. Fixed. (Bug #31775)
#184476 **
Excessive wildcard use in client views could crash the
ntx64/p4d server under circumstances that would be handled
correctly by the ntx86/p4d server. It was discovered
that the 64-bit version of the windows server requires more
stack space to perform commands involving excessive wildcard
usage in client mappings. This has been resolved so that the
ntx6/p4d process behaves similarly to the ntx86/p4d.
(Bug #31737) (Only the first 15 lines of the commit message are shown above )
|
Fri, 2 Jan 2009
|
[ 20:46 lth ]
Update distpaths.
Pointy hat to: me
|
Mon, 29 Dec 2008
|
[ 14:38 lth ]
- Update to 08.2
- Drop alpha support
- Fix log dir location [1]
- Fix depot permissions [1]
- Separate DIST_SUBDIR [2]
Submitted by: Bernard Treves Brown [1], infofarmer [2]
|
Sun, 27 Apr 2008
|
[ 12:47 lth ]
Bugs fixed (from release notes):
#152382 **
Sometimes 'p4 integrate' would find a distant base when
cherry picking revisions to integrate. Now 'p4 integrate'
insists that the base be the revision before the first
revision being integrated when cherry picking revisions.
(Bug #29016).
#152296 **
'p4 submit' could report "No files to submit" if the
combination of client mapped files and protections table
exceeded an internal limit. This limit was incorrectly
reached on case-insensitive Servers (Windows) by repeated
values in a generated map. This has been fixed. (Bug #28853)
|
Thu, 10 Apr 2008
|
[ 08:29 lth ]
Bugs fixed (from release notes):
#149704 **
'p4 integrate' could skip integrations in the face of
large branch views coupled with large protection tables.
This has been corrected. (Bug #28659)
#149538 **
'p4 integrate' could report "no permission on file(s)" if
the protections managed by 'p4 protect' had excessive wildcards
(too many ...'s in too many entries). Now 'p4 integrate'
should be no more sensitive than other commands to the number
of wildcards in protections, and in any event should fail
with a more appropriate message ("too may wildcards").
(Bug #28422).
Changes: http://www.perforce.com/perforce/doc.073/user/relnotes.txt
|
Mon, 14 Jan 2008
|
[ 15:10 lth ]
Missed two new distinfo files
|
Number of commits found: 10 |