On Wed, 5 Mar 2003, MKlinke wrote:
> It's easy to overlook. It isn't the file that dictates the revision ID.
> It's the module; from the manual ...
Huh. Well, it looks like I can specify the revision at the first commit by
specifying just the major number (e.g. cvs commit -r 1) so this isn't a
It's easy to overlook. It isn't the file that dictates the revision ID.
It's the module; from the manual ...
"When adding a new file, the second number will always be one and the
first number will equal the highest first number of any file in that
directory. For example, the current directory
On Wed, 5 Mar 2003, MKlinke wrote:
> From the text, my guess is that you have another file in the module that
> has a 2.x revision ID so the newly assigned internal number would
> automatically be 2.1.
By definition, a new file in a module does not *have* a previous
revision, so this would not b
From the text, my guess is that you have another file in the module that
has a 2.x revision ID so the newly assigned internal number would
automatically be 2.1.
Regards, Mike Klinke
On Wednesday 05 March 2003 09:21, Todd A. Jacobs wrote:
> I have a weird little CVS problem that I was wonderin
I have a weird little CVS problem that I was wondering if anyone else had
ever encountered. Whenever I create a new file in an existing module, it's
created as revision 2.1 instead of 1.1.
This isn't really mission critical, but it sure is annoying. Anyone have
any idea what coul
Title: Message
Hi all,
This is not 100% linux related
problem but still i hope will get feedbacks. I installed WINCVS
client on win2k m/c and trying to connect Linux CVS server. So far its working
fine and checked out source also but now when i try to connect, its exiting with
code 1 and
I'm trying to compile KDE from CVS as there are some features that I
need. I've never tried to compile from CVS (anything) before, so I'm
very lost in what the problem might be. I'm using a script from the KDE
site called 'kde-cvsbuild-0.1.5' to gather, build, etc the files. I'm
running in
