[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: improper behavior or improper usage?
From: |
Andy Jones |
Subject: |
RE: improper behavior or improper usage? |
Date: |
Fri, 10 Oct 2003 09:04:16 +0100 |
On Friday, October 10, 2003 6:00 AM, Larry Jones
[SMTP:address@hidden wrote:
> Mark Jaffe writes [in exceedingly long lines]:
> >
> > CVS is not behaving as expected, and causing great difficulty.
>
> Your expectations are wrong. The CVS philosophy is that you tag entire
> modules, not bits and pieces.
>
> -Larry Jones
I think Larry is right in that Lawrence's expectations are wrong. But I
think the problem is something different.
Lawrence, if I understand correctly, you are tagging files that are ready
to become part of the main product, then trying to check out a working copy
that is the sum of the 'main product' tag and the 'ready' tag?
This is contrary to CVS's normal mode of working. Normally you check out a
working copy, do the development, then *commit* files to make them part of
the product. You can then export or checkout to a common code area if you
need to.
If this doesn't work for you, why not just have a 'current product' tag,
and add or remove it from files as necessary? But by doing this you are
circumventing a lot of the good stuff CVS has to offer.
What we will be doing here is: every time we are ready to make a release,
tag all the files for that release with a 'release' tag. Then we can
export on just that tag. We can tag individual files if we like (for
example if we are making a patch release and only need some of the 'library
routines' module) and that works fine.
Andy Jones
Tapestry Software.