Relevant since our build server was down.

Quoted: This note describes how to reconcile your Perforce client information with workspace changes made outside of the system, and how to build a changelist after the fact.

Shelving is a good feature. We used to use a script called bbpack to achieve something similar on top of Source Depot (derivative of Perforce). I am trying to find something similar for Perforce.

Quoted: Shelving alleviates the problems posed by having a daily check-in. With TFS, you save a copy of your current changes to the source control repository at the end of the day. However, as part of this process, you indicate that the source code isn't ready for others to retrieve. The code is put on the shelf, so to speak. Only you will be able to access the shelved version. That way, your daily changes to the source code are backed up, but other team members won't be able to access the unfinished code.

I had never thought of using source control to do "backups" of settings and documents files. Make sense. I'm going to set up a subversion server for this purpose.

Quoted: I have a Subversion repository that contains stupid stuff like my .emacs file, and then I have some personal wiki's and blogs that use files or mysql dbs under the covers.