[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Tue, 25 Oct 2005 03:21:05 -0400
On Mon, Oct 24, 2005 at 11:22:33PM -0700, bill pursell wrote:
> I've glanced very briefly at the cvs plugins for vim, but I like things
> to be simple, and I fear change :) The thing is, I often find myself
> annoyed by cvs behavior, and a lot of times I end up copying the rcs
> files out of the repository and getting what I want with rcs and then
> merging my changes back in. I'm somewhat concerned about that, as it
> is clearly not the proper behaivor, but it's often so much easier than
> building the entire working directory just to get one particular
> revision of one particular file. Building the directory path down to
> the file with 'cvs co -r2.7 path/to/foo' is annoying when all I want is
cvs co -r 2.7 -d bar foo path/to/foo
to create bar/foo instead of path/to/foo...
At least this removes the depth of the tree.
And yes, your approach sounds very dangerous and
single-developer-centric, in other words, not at all conducive to
multiple developers working on a project, as it sounds like such a
situation (and that's a situation for which CVS was most directly
designed) would result in utter chaos with no hope of restoration
without reference to a backup...
Doug Lee address@hidden http://www.dlee.org
SSB + BART Group address@hidden http://www.bartsite.com
"Sometimes I think my learning curve is a circle." -- David Andrews