[cvsnt-dev] Re: Should a recent CVSNT server compatable with a CVS 1.11.19 client

[Matt Schuckmann]

Thanks for the reply Tony.

I'm testing it out and things look ok but I get some funny behaviour when
committing.

Given the example command and output below right away I see 2 strange
things.

1. Should I be worried about the lines 'cvs server: Unknown expansion option
...'
2. It committed all three files in the simple sandbox even though I
specified only a.cpp, maybe this is a side effect of -f option that I'm not
aware of.

Thanks
Matt S.


Example:

dpp999:simple>cvs commit -f -m"" a.cpp
cvs commit: Examining .
cvs server: Unknown expansion option 'T'.
cvs server: Unknown expansion option 'H'.
cvs server: Unknown expansion option 'E'.
cvs server: Unknown expansion option 'A'.
cvs server: Unknown expansion option 'T'.
cvs server: Unknown expansion option 'H'.
cvs server: Unknown expansion option 'E'.
cvs server: Unknown expansion option 'A'.
cvs server: Unknown expansion option 'T'.
cvs server: Unknown expansion option 'H'.
cvs server: Unknown expansion option 'E'.
cvs server: Unknown expansion option 'A'.
Checking in a.cpp;
/CVSTestData/simple/a.cpp,v  <--  a.cpp
new revision: 1.4; previous revision: 1.3
done
Checking in b.cpp;
/CVSTestData/simple/b.cpp,v  <--  b.cpp
new revision: 1.3; previous revision: 1.2
done
Checking in c.cpp;
/CVSTestData/simple/c.cpp,v  <--  c.cpp
new revision: 1.4; previous revision: 1.3
done



"Tony Hoyle" <tmh at nodomain.org> wrote in message
news:d31qlp$ahq$1 at paris.nodomain.org...
> Matt Schuckmann wrote:
> > So my question is will a standard CVS client (version 1.11.19) play nice
> > with a current CVSNT server?
> >
> > I realize that the standard CVS client won't have all the features of
the
> > CVSNT client but will it work ok?
> >
> It should do... it's a standard protocol.
>
> Tony