Hi,
I am trying to get cvs (v1.9.29) pserver up and running under OS/2 Warp.
I have followed the readme and started inetd and added cvs to inetd.lst
as "cvspserver tcp cvs --allow-root=f:\cvsroot\". I have added an entry
to services. And all that is working ok - but when ever I try to login I
get
On Tue, Jan 16, 2001 at 19:40 -, rjd wrote:
> CVS version 1.10.7
>
> CVS log shows revision 1.1.4 on 2000-05-10 and 1.1.5 on
> 2000-05-15 for file "filename".
>
> I entered cvs diff -D2000-05-10 -D2000-05-15 filename
> CVS showed nothing.
>
> I entered cvs diff -r1.1.4 -r1.1.5 filename
>
Derek Scherger writes:
>
> I know I've read that the cvswrappers/commitinfo/etc. functionality
> doesn't work well (or at all?) when using :pserver: repositories and I'm
> wondering if it does work better if :ext: is used instead?
No. The problems affect all client/server methods equally. In
rjd writes:
>
> CVS version 1.10.7
You really ought to upgrade (www.cvshome.org).
> CVS log shows revision 1.1.4 on 2000-05-10 and 1.1.5 on 2000-05-15
> for file "filename".
>
> I entered cvs diff -D2000-05-10 -D2000-05-15 filename
> CVS showed nothing.
>
> I entered cvs diff -r1.1.4 -r1.1.
I am having the exact same problem. I am running a WinCVS client
trying to commit changes to a UNIX CVS server. I can check files out,
but I cannot commit due to the error below. This seems like a pretty
common configuration - has there been any resolution to this issue? I
have tried setti
CVS version 1.10.7
CVS log shows revision 1.1.4 on 2000-05-10 and 1.1.5 on 2000-05-15
for file "filename".
I entered cvs diff -D2000-05-10 -D2000-05-15 filename
CVS showed nothing.
I entered cvs diff -r1.1.4 -r1.1.5 filename
CVS showed differences.
Ought not the two commands show the same ou
Saima Iqbal writes:
>
> tried making the parent directory read only, but then that interferes with the
> checkout of the directories within.
You can use LockDir in CVSROOT/config to put the locks somewhere else
and avoid that problem.
-Larry Jones
OK, there IS a middle ground, but it's for sis
Hi,
I was wondering if there is a way to lock all but a few selected
users from creating directories/files at a certain level in a repository. I
tried making the parent directory read only, but then that interferes with the
checkout of the directories within. The objective is to ke
I know I've read that the cvswrappers/commitinfo/etc. functionality
doesn't work well (or at all?) when using :pserver: repositories and I'm
wondering if it does work better if :ext: is used instead?
What I'm looking for is a way of enforcing formatting (running indent
etc.) and doing some other
Alan Weston wrote:
>
>Hello, I'm completely new to CVS and versioning so please be nice.
>How does one use CVS whilst maintaining the advantages of the more
>traditional approach of migrating code from a development environment
>once unit tested to a test environment for system and cycle test
[EMAIL PROTECTED] writes:
>
> Hello, I'm completely new to CVS and versioning so please be nice.
> How does one use CVS whilst maintaining the advantages of the more
> traditional approach of migrating code from a development environment
> once unit tested to a test environment for system an
Larry Jones wrote:
> The CVS command in inetd.conf is incorrect -- most likely, you're
> missing the "pserver" on the end. Check that the command is all on one
> line and doesn't contain any invisible control characters.
That did the trick. It's funny how it's the "little" things that will
bi
Jason Lee writes:
>
> cvs [login aborted]: unrecognized auth response from : Usage: cvs
> [cvs-options] command [command-options-and-arguments]
The CVS command in inetd.conf is incorrect -- most likely, you're
missing the "pserver" on the end. Check that the command is all on one
line and does
Hello, I'm completely new to CVS and versioning so please be nice.
How does one use CVS whilst maintaining the advantages of the more
traditional approach of migrating code from a development environment
once unit tested to a test environment for system and cycle testing
and ultimatley to a
Robert Longworth writes:
>
> 1 conflicts created by this import.
> Use the following command to help the merge:
>
> cvs checkout -jVEND:yesterday -jVEND testapp
The suggested command assumes you won't import more than one vendor
release per day, which you have. It is much safer to use th
Howard Zhou writes:
>
> I'd like to add *.gif and *.jpg as binary type in the CVSROOT/cvswrapper. I
> wonder what impact would be to the existing *.gif and *.jpg files since they
> were commited as regular text file type in the past.
CVSROOT/cvswrapper has no affect on existing files; if you wan
When trying to log in to cvs via pserver, I get this response:
cvs [login aborted]: unrecognized auth response from : Usage: cvs
[cvs-options] command [command-options-and-arguments]
The user exists on the target system, and I've set up the user in the
password file (which I added to the CVSROO
Robert,
> I guess it is, because on WinCVS there is a description
> using ssh 1.2x (I could not find that stuff anywhere on
> the net, so I assume it is *some* outdated, though).
Install CygWin, it comes with ssh (OpenSSH) and it's pretty forward. It
works with cvs/cygwin, cvs/wincvs and WinCvs.
First off, please reply back to [EMAIL PROTECTED] as well as me. I don't
consider these questions off topic.
You can find the original cvs-1.10.8 source from (I think) OpenAvenue. I'm not
sure exactly what source is at SourceForge.
Since I'm not currently using CVS, I won't be doing the merge
This is both the curse and the blessings of open source development. On one
hand, you are able to fix problems on your own. On the other hand, you many
need to maintain those fixes.
I can't completely blame the CVS maintainers for not using my patches.
According to the HACKING file, I'm suppose
Hi All,
I've been reading this list for a while but haven't seen a solution to this
problem yet, it basically concerns merging the changes we make to some
source with the changes present in the next vendor release. This is what I
did to test the problem.
I had four identical files file1.txt file
21 matches
Mail list logo
