[p4] Marking a file "do not submit"?

[Strelzyk, Stephen]

Why don't you just put this file in a numbered changelist by itself, and
you won't have the problem?

A standard practice that I follow and instruct all of our developers is
to always put your files into number changelists after performing the
checkout.  This is a little more tedious if you are using an SCC plugin,
so we recommend not using  the SCC plugins for Visual Studio 2005 at our
location.

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Roy Smith
Sent: Saturday, July 28, 2007 9:25 AM
To: Perforce Users Mailing List
Subject: [p4] Marking a file "do not submit"?

Is there a way to mark an open file, "do not submit"?

We just had an incident of somebody submitting a change which  
consisted of several files he wanted to submit, plus one that was  
picked up by accident.  The accidental one was an experimental idea  
he'd been working on for a long time in a different part of the  
tree.  He probably forgot that he still had it open and didn't look  
at the list of file in the changlist too closely, so it got submitted  
by accident.

This isn't the first time it's happened (to various people, including  
myself).

If there was a way to mark a file, "still open for editing, but don't  
ever include in a default changelist".  This will let you keep edited  
files around for a long time without risking accidental submissions  
like this.  I know, I know, you really should make a new branch for  
stuff like this, but sometimes that's more overhead than it's worth.

-------------------
Roy Smith <smith_roy at emc.com>
Software Guy, EMC Common Management Group
44 South Broadway, 7th floor
White Plains, NY 10601
(914) 580-3427
AIM: roysmith649

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user