git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] cvsimport: die on cvsps errors

From
Jeff King <peff@peff.net>
Date
Dec 24, 2007, 03:08 UTC
Message-ID
<20071224030819.GA15485@sigill.intra.peff.net>
In-Reply-To
<20071224030551.GA12495@sigill.intra.peff.net>

We were not previously checking the exit status of cvsps at all. If it exited before producing any useful output, we ended up with an empty import, which caused a spew of confusing error messages from other parts of git:

$ git-cvsimport foo Initialized empty Git repository in ... some error from cvsps fatal: refs/heads/origin: not a valid SHA1 fatal: master: not a valid SHA1 warning: You appear to be on a branch yet to be born. warning: Forcing checkout of HEAD. fatal: just how do you expect me to merge 0 trees? checkout failed: 256

Now we get:

$ git-cvsimport foo Initialized empty Git repository in ... some error from cvsps git-cvsimport: fatal: cvsps reported error

Signed-off-by: Jeff King <peff@peff.net>
---
On Sun, Dec 23, 2007 at 10:05:51PM -0500, Jeff King wrote:
> That being said, it's awful that git-cvsimport doesn't stop when cvsps
> exits with an error, producing all of those meaningless errors. Patch
> will follow.
And here it is.
 git-cvsimport.perl |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/git-cvsimport.perl b/git-cvsimport.perl
index 1fa9a22..6d8ff93 100755
--- a/git-cvsimport.perl
+++ b/git-cvsimport.perl
@@ -632,6 +632,7 @@ unless ($opt_P) {
 	    print $cvspsfh $_;
 	}
 	close CVSPS;
+	$? == 0 or die "git-cvsimport: fatal: cvsps reported error\n";
 	close $cvspsfh;
 } else {
 	$cvspsfile = $opt_P;
-- 
1.5.4.rc1.1119.g1e6bc-dirty
Previous: Jeff KingNext: Martin Langhoff
Message 7 of 9 in “cvsimport: trying to convert freebsd cvs to git”
  1. Miklos VajnaDec 22, 2007
  2. Anand KumriaDec 23, 2007
  3. David Soria ParraDec 23, 2007
  4. Jeff KingDec 23, 2007
  5. Martin LanghoffDec 23, 2007
  6. Jeff KingDec 24, 2007
  7. cvsimport: die on cvsps errorsJeff King, Dec 24, 2007
  8. Martin LanghoffDec 24, 2007
  9. Miklos VajnaDec 24, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.