# Note: We use REPL_MAILFROM rather than REPL_MAILTO, since # REPL_MAILFROM is guaranteed to be a single email address, # where REPL_MAILTO might be a list of addresses. Syntatically, # a single email address is required here. User: REPL_OSUSER Email: REPL_MAILFROM FullName: Perforce Admin Type: standard
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #3 | 25596 | tom_tyler |
Released SDP 2019.2.25594 (2019/05/02). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
| #2 | 25245 | tom_tyler |
Released SDP 2019.1.25238 (2019/03/02). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
| #1 | 21290 | tom_tyler |
Updated HMS tight ship setiup script; now passes preliminary tests. Bypassing pre-commit review for work-in-progress development of new, unreleased functionality. |
||
| //guest/perforce_software/sdp/main/Server/Unix/setup/hms/perforce.user.p4s | |||||
| #1 | 21081 | tom_tyler |
Added preliminary files in support of automation of the HMS Tight Ship installation. The key file here hs hms_ts_setup.sh, which is currently a 'doc only' script that documents what it is intended to do, although it doesn't currently do anything that affects data. The '-h' and '-man' flags work to convey their intent. This also contains various spec files to be used in the actual implementation. Bypassing pre-commit review since this is only adding new 'doc only' code, not active software. #review-21082 |
||