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

[Jeff Jensen]

I second that practice of putting the files in a separate pending
changelist.

I have trained the team to do just that, and it works very well.  In fact,
everyone is encouraged to always have the default changelist empty, creating
separate changelists for all work in progress.  Thus:
 - any file found in default needs dispositioning - moved to the correct
pending or reverted
 - nearly all submissions come from numbered pendings
 - few to no errant checkins
 - improved commit comments as you can add to them as you go

Since most developers concurrently work on a few things (local overrides,
experiments, new features, bug fixes...), we each usually have at least a
few pendings.


Whenever I have to use a different SCM than Perforce, it is the first thing
I miss - pending changelists to organize work.  It is a glaring omission to
me in other SCMs!


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

Put it in its own changelist and make the description of the changelist
"DO NOT SUBMIT!!!".

If it's a particular type of file and it's a serious enough a problem
for the effort, write a trigger that either prevents checkin of that
type or only allows it on a second attempt, giving an "Are you sure?"
message on the failure.

Steve

Roy Smith wrote:
> 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
>
>   

-- 
Stephen Vance
www.vance.com
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user