Re: CVS - setup reserved checkout

[Kathryn Huxtable]

"Kaz Kylheku" <address@hidden> wrote in message
news:address@hidden
> In article <address@hidden>, Greg Cooper
wrote:
> >David Masterson <address@hidden> wrote in message
news:<address@hidden>...
> >> >>>>> Andrew  writes:
> >>
> >> > Has anyone setup reserved checkout in CVS (ver 1.11.1p1) in Unix
> >> > (Solaris)? Or is there any documentation on this other than the
> >> > manual that comes with the source code?
> >>
> >> Given the CVS model of unreserved checkouts, why do you need reserved
> >> checkouts?  Also, are you talking about reserved checkouts of a file
> >> or an entire product?
> >
> >We use CVS (ver 1.11) and we like the unreserved checkout model, but
>
> The what model? You seem to still be clinging to the biased terminology
> used by the vendors of inferior version control tools. ``Unreserved''
> is a negative word that suggests risk and hassle, like an
> unreserved airplane ticket, restaurant table or hotel room.

I would add that instead of thinking of "checkout" you should think in terms
of updates and commits. Before you start working on something, update your
source. That way, you get the most recently committed changes. When you're
done, you commit your changes. The key is to provide positive terminology
that they can decide they like.

The comments about granularity that I didn't quote are quite apropos.

-K