[p4] Re: Implement a "p4 checkout" (Michael Graff)
swiegand at Adobe.COM
Fri Jan 7 01:20:54 PST 2000
this might me true for text files, but we have got a lot of binary files,
which can't be merged (they are frequently edited). So what would you
suggest here if not exclusive checkout?
> Hi Mike --
> My strong suggestion to you is to handle it the same way I handled it
> told them up front how to use the resolve command. (Took about 5 minutes a
> customer) and then told them to use it. For the first couple of weeks I
> people come up to me saying "You have the file checked out that I need".
Or "I am
> editting a file that you have checked out". To which my universal reply
> rather brutal, but effective reply of "So what? Do you think you made a
> mistake that you want me to look at?" (Actually, it was a little politer
> that) But the point was made very clear that this was no longer an issue.
> know what? Everyone got the idea that Perforce could deal with these
> But if you give them training wheels you will convince them that the
> in perforce not their assumptions.
> Toss the training wheels. They will figure it out.
> > Our folks are accustomed to serial checkouts where the first person to
> > check out the file has a lock on it. They can't check out a file if
> > somebody already has it locked. I'd like to make Perforce work this way
> > default.
> > I see the SCC plugin has a "lock" option that works this way. If it
> > get a lock, it gives a warning and reverts the file. Here's an example:
> > Checking out and locking files.
> > file://depot/Desktop/AJMGR.CPP#5 - opened for edit
> > file://depot/Desktop/AJMGR.CPP - locked by THEOTHERGUY at theother
> > file://depot/Desktop/AJMGR.CPP - already locked by THEOTHERGUY at theother
> > The following files were not opened because they could not be locked:
> > AJMGR.CPP
> > file://depot/Desktop/AJMGR.CPP#5 - was edit, reverted
> > I'm looking for a similar feature in P4WIN, but I didn't find it. Edit
> > lock seem to require separate actions. Did I miss an option somewhere?
> > I'd also like to do something similar at the command line. A "p4
> > or "p4 editlock" command would be the most obvious, but if I could
> > duplicate the SCC "could not be locked" function with a wrapper, that
> > be okay too. I notice that if I do a "p4 lock" I always get a zero
> > code whether the lock happened or not.
> > So, how does the SCC get the list of files that couldn't be locked?
> > it just parse the output of the lock command?
More information about the perforce-user