[Top][All Lists]

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

Re: Weird revision number on trunc.

From: Sergei Organov
Subject: Re: Weird revision number on trunc.
Date: Mon, 16 Jul 2007 17:40:44 +0400
User-agent: Gnus/5.110006 (No Gnus v0.6) XEmacs/21.4.20 (linux)

Yves Dorfsman <address@hidden> writes:
> On Mon, 16 Jul 2007, Sergei Organov wrote:
>> Then, after committing yet another change to the file, I get normal
>> revision 1.2, so it doesn't seem to be real problem, except CVS behavior
>> is really confusing in this case. What made it even more confusing is
>> that in the real repository the second import was made by mistake (I
>> suppose using some button in the WinCVS front-end).
> If you use Wincvs, then you should use the macros:
> -CVS --> Create root module
> and
> -Add --> Recursive Add
> This way you can check in an entire directory with "normal" revision
> number.

No, I don't use Wincvs myself, though a few of our developers do. I
think that with your help I now understand what has happened, and we
hopefully already fixed the repository by committing correct versions of
files onto the trunc. The only issue that remains is how to prevent that
from happening in the future. I don't currently see any other way than
training those Wincvs users to avoid cvs imports.

Is there a way to disable 'cvs import' on per-repository or even
per-server-installation basis, except changing sources and re-build? 

[I did feel "cvs import" to be an evil from very beginning, but didn't
expect it will finally bite me after 10 years of CVS use and


reply via email to

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