help with CVS use case

[Hoehle, Joerg-C. <Joe...@t-...>]

Hi,

this is a query about how you people use CVS.

Let's suppose I have a CVS tree and I'm working on many changes =
affecting lots of files. Of course, I'm busy for several days doing so. =
In between, my stuff may not even compile.

1. Should I update inbetween? Why?
The risk I see is that, instead of being able to continue my work, I'd =
have to spend time figuring out why the update may not work, or merge =
or whatever. All things which prevent me from making progress.


Now let's suppose I see a bug-report that I could fix, or I have some =
idea about a tiny little thing to add, independent on the above =
middle-term work.

2. How can I submit a tiny patch just for this topic?
2a if it affects a file different from the above work?
2b if it affects a file that I'm currently working on, but in an =
unrelated region?

Is checking-out a completely new copy into another directory tree all =
that is available?
That would mean a ratio of 70MB ('du' on a make 'full' tree) for 500 =
bytes worth of the patch!?

Thanks for your help,
	J=F6rg H=F6hle.