Discussion of Spells and Grimoire items

[Eric Sandall <eric AT sandall.us>]

Quoting Andrew <afrayedknot AT thefrayedknot.armory.com>:
<snip> 
> perhaps the file could have a brief explaination of why not to integrate.

This is a good idea, especially if the 'lock' may be there for a while and we
forget.

> Does perforce have a way of preventing integration, or at least warning
> beforehand?

$ p4 help commands
...
lock       Lock an opened file against changelist submission
...

$ p4 help lock
 
    lock -- Lock an opened file against changelist submission
 
    p4 lock [ -c changelist# ] [ file ... ]
 
        The open files named are locked in the depot, preventing any
        user other than the current user on the current client from
        submitting changes to the files.  If a file is already locked
        then the lock request is rejected.  If no file names are given
        then lock all files currently open in the changelist number given
        or in the 'default' changelist if no changelist number is given.

So it sounds like you'd either have to leave it open without submitting the
changes, or you can submit the changes, reopen, then lock.

> -Andrew

-sandalle

-- 
PGP Key Fingerprint:  FCFF 26A1 BE21 08F4 BB91  FAED 1D7B 7D74 A8EF DD61
http://search.keyserver.net:11371/pks/lookup?op=get&search=0xA8EFDD61

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS/E/IT$ d-- s++:+>: a-- C++(+++) BL++++VIS>$ P+(++) L+++ E-(---) W++ N+@ o?
K? w++++>-- O M-@ V-- PS+(+++) PE(-) Y++(+) PGP++(+) t+() 5++ X(+) R+(++)
tv(--)b++(+++) DI+@ D++(+++) G>+++ e>+++ h---(++) r++ y+
------END GEEK CODE BLOCK------

Eric Sandall                     |  Source Mage GNU/Linux Developer
eric AT sandall.us                  |  http://www.sourcemage.org/
http://eric.sandall.us/          |  SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/  #196285  |  http://www.shock.wsu.edu/

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.