02.05.2013 Views

The Source Integrity Professional Edition User Guide - MKS

The Source Integrity Professional Edition User Guide - MKS

The Source Integrity Professional Edition User Guide - MKS

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Managing Archives and Revisions<br />

Microsoft’s Messaging Application Program Interface results in a<br />

mail notification dialog box that lets you send email to the user<br />

whose lock you are breaking.<br />

Note Although you may not be prohibited from breaking some else’s<br />

lock, you should be cautious about doing so, since it can result in<br />

confusion and duplication of effort in shared working environments. For<br />

information on permissions, see “Security and Administration” on<br />

page 34.<br />

To unlock a revision in the Windows interface:<br />

1. Select a locked revision in the Archive window, one that has a<br />

padlock symbol ( ).<br />

2. Choose Archive > Unlock Revision or click .<br />

<strong>The</strong> padlock symbol and the name of the user who had the<br />

revision locked both disappear.<br />

To unlock a revision in the <strong>Source</strong> <strong>Integrity</strong> Web Interface:<br />

Select a locked revision in the Member, Sandbox, or Project views and<br />

choose Unlock.<br />

To unlock a revision in the command line interface:<br />

Use the rcs command with the -u option. Its syntax is<br />

rcs -u[rev]<br />

where rev is the revision number. If a branch is given, the latest<br />

revision on that branch is unlocked. If rev is omitted, any revision<br />

locked by the user is unlocked. If no such revision exists, the most<br />

recent lock that has been set is removed, if there is one.<br />

188 <strong>Source</strong> <strong>Integrity</strong> <strong>Professional</strong> <strong>Edition</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!