[p4] Re: Implement a "p4 checkout" (Michael Graff)

[Stefan Wiegand]

Hi Pat,

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?

Stefan


> Hi Mike --
>
> My strong suggestion to you is to handle it the same way I handled it
here. I
> 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
had
> 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
was the
> rather brutal, but effective reply of "So what? Do you think you made a
coding
> mistake that you want me to look at?" (Actually, it was a little politer
than
> that) But the point was made very clear that this was no longer an issue.
And you
> know what? Everyone got the idea that Perforce could deal with these
issues.
>
> But if you give them training wheels you will convince them that the
problem lies
> in perforce not their assumptions.
>
> Toss the training wheels. They will figure it out.
>
> -Pat
>
>
> >
> > 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
by
> > default.
> >
> > I see the SCC plugin has a "lock" option that works this way.  If it
can't
> > 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
and
> > 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
checkout"
> > or "p4 editlock" command would be the most obvious, but if I could
easily
> > duplicate the SCC "could not be locked" function with a wrapper, that
would
> > be okay too.  I notice that if I do a "p4 lock" I always get a zero
return
> > code whether the lock happened or not.
> >
> > So, how does the SCC get the list of files that couldn't be locked?
Does
> > it just parse the output of the lock command?