From: "Cameron McBride" <cameron.mcbride@gmail.com>
To: git@vger.kernel.org
Subject: git-cvsserver wart?
Date: Thu, 25 May 2006 12:42:49 -0400 [thread overview]
Message-ID: <dcedf5e20605250942g6a7417dfh5f2f26df29842def@mail.gmail.com> (raw)
I'm a new git user, so if I'm doing something boneheaed - sharp kicks
are welcome.
For reasons I won't go into, the ability to use cvs clients is darn
near crucial. Although most development is local (where I install /
use git), pulling down the latest updates and pushing up minor changes
via CVS is helpful at remote locations where I don't want to maintain
clients. Git with git-cvsserver makes this very nice. Thanks to
all!
Now, the problem I ran into:
code/ntropy> cvs up
Can't use an undefined value as an ARRAY reference at
/usr/local/bin/git-cvsserver line 761.
closing dbh with active statement handles
cvs [update aborted]: end of file from server (consult above messages if any)
code/ntropy> cvs -v
Concurrent Versions System (CVS) 1.11.1p1 (client/server)
Doing a 'cvs up -dP' (or either of the two individually) seems to work fine.
so, it's an old client, a newer client doesn't have this problem. a
bare 'cvs up' works fine on:
Concurrent Versions System (CVS) 1.11.17 (client/server)
Just to be clear, it appears everything gets updated with the
workaround - but there might be something else amiss, so I thought it
was worth mentioning.
Cameron
p.s. I'm assuming the following statement is harmless (it's always present):
closing dbh with active statement handles
next reply other threads:[~2006-05-25 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 16:42 Cameron McBride [this message]
2006-05-25 21:19 ` git-cvsserver wart? Martin Langhoff
2006-05-26 3:11 ` Cameron McBride
2006-05-26 3:23 ` Martin Langhoff
2006-05-26 3:57 ` Cameron McBride
2006-05-26 3:24 ` Cameron McBride
2006-05-26 3:28 ` Martin Langhoff
2006-05-26 3:34 ` Cameron McBride
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dcedf5e20605250942g6a7417dfh5f2f26df29842def@mail.gmail.com \
--to=cameron.mcbride@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).