[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CVS Update Behaviour
From: |
Greg A. Woods |
Subject: |
Re: CVS Update Behaviour |
Date: |
Thu, 21 Feb 2002 13:19:30 -0500 (EST) |
[ On Thursday, February 21, 2002 at 11:06:28 (+0000), Colm Murphy wrote: ]
> 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 lead
> 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.
--
Greg A. Woods
+1 416 218-0098; <address@hidden>; <address@hidden>; <address@hidden>
Planix, Inc. <address@hidden>; VE3TCP; Secrets of the Weird <address@hidden>
- CVS Update Behaviour, Colm Murphy, 2002/02/21
- Re: CVS Update Behaviour, Arcin Bozkurt - Archie, 2002/02/21
- Re: CVS Update Behaviour, Greg A. Woods, 2002/02/21
- Re: CVS Update Behaviour, Arcin Bozkurt - Archie, 2002/02/21
- Re: CVS Update Behaviour, Greg A. Woods, 2002/02/21
- Re: CVS Update Behaviour, Paul Sander, 2002/02/21
- Re: CVS Update Behaviour, Greg A. Woods, 2002/02/22
- Re: CVS Update Behaviour, Paul Sander, 2002/02/22
- Re: CVS Update Behaviour, Greg A. Woods, 2002/02/22