[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CVS Update Behaviour

From: Arcin Bozkurt - Archie
Subject: Re: CVS Update Behaviour
Date: 21 Feb 2002 18:06:53 -0500

[ On Thursday, February 21, 2002 at 11:06:28 (+0000), Colm Murphy

> Subject: CVS Update Behaviour
> All is fine until the developer does an cvs update.
> The current behaviour is that all existing files are updated (which is
> fine) but all other files in the directory are checked out.
> This is more of an annyoance than anything else, but it can easily
> to tagging files which aren't part of the module you are working on.
> (if you use cvs tag).

It sounds like you really need to re-organise your fundamental
repository structure so that the files that are used together are
grouped alone in their own directories.  There are many other advantages
to such a more structured organisation over and above how well it works
with CVS.


This is exactly what i have to do now, with our current structure. A
huge project has to be broken down into different modules. Some will be
subdirectories of the existing modules, but I want to put some into a
seperate module...

suppose I created a branch at this point (for bugfixes) and later
restructured the repository moving files around. I believe there is not
way to merge the bugfixes back any more since they are not in the same
module anymore...

How do I get around this problem?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]