git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean-Luc Herren <jlh@gmx.ch>
To: git@vger.kernel.org
Subject: git cvsimport fails noisily if cvs has no server support
Date: Sun, 03 Feb 2008 16:28:24 +0100	[thread overview]
Message-ID: <47A5DD98.6000606@gmx.ch> (raw)

Hello list!

cvs (1.12.12) can be compiled with --disable-server to omit
support for cvs servers.  Although this is not ./configure's
default, it was the default on my distro (gentoo).  git-cvsimport
fails loudly as pasted below (note that this command is part of
the test t9600-cvsimport.sh).  Nicer behavior would of course be
to detect the situation and inform the user that server support is
missing (and to skip the test).

jlh

$ git-cvsimport -a -z 0 -C module-git module
Unknown command: `server'

CVS commands are:
        add          Add a new file/directory to the repository
        admin        Administration front end for rcs
[...26 lines omitted...]
        watch        Set watches
        watchers     See who is watching a file
(Specify the --help option for a list of other help options)
Use of uninitialized value in scalar chomp at /home/jlh/cvs/git/t/../git-cvsimport line 345.
Use of uninitialized value in substitution (s///) at /home/jlh/cvs/git/t/../git-cvsimport line 346.
Expected Valid-requests from server, but got: <unknown>
$ 

             reply	other threads:[~2008-02-03 15:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 15:28 Jean-Luc Herren [this message]
2008-02-03 18:08 ` git cvsimport fails noisily if cvs has no server support Robin Rosenberg
2008-02-04 15:27   ` [PATCH] git-cvsimport: Detect cvs without support for server mode Jean-Luc Herren
2008-02-05  9:08     ` Junio C Hamano
2008-02-05 13:03       ` Jean-Luc Herren

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=47A5DD98.6000606@gmx.ch \
    --to=jlh@gmx.ch \
    --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).