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

[PATCH] git-cvsimport.perl: Print "UNKNOWN LINE..." on stderr, not stdout.

From
Jim Meyering <jim@meyering.net>
Date
Aug 5, 2008, 14:54 UTC
Message-ID
<87zlnro6kt.fsf@rho.meyering.net>
Signed-off-by: Jim Meyering <meyering@redhat.com>
---
I'm used to filtering git-cvsimport's noisy stderr, but this
diagnostic appears on stdout.  Looks like an oversight.
Now that I'm using cvsps-2.2b1, I see tons of these.
 git-cvsimport.perl |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/git-cvsimport.perl b/git-cvsimport.perl
index e2664ef..e439202 100755
--- a/git-cvsimport.perl
+++ b/git-cvsimport.perl
@@ -952,7 +952,7 @@ while (<CVS>) {
 	} elsif (/^-+$/) { # end of unknown-line processing
 		$state = 1;
 	} elsif ($state != 11) { # ignore stuff when skipping
-		print "* UNKNOWN LINE * $_\n";
+		print STDERR "* UNKNOWN LINE * $_\n";
 	}
 }
 commit() if $branch and $state != 11;
--
1.6.0.rc1.36.g5ff70
Next: Jeff King
Message 1 of 4 in “git-cvsimport.perl: Print "UNKNOWN LINE..." on stderr, not stdout.”
  1. git-cvsimport.perl: Print "UNKNOWN LINE..." on stderr, not stdout.Jim Meyering, Aug 5, 2008
  2. Jeff KingAug 5, 2008
  3. Jeff KingAug 5, 2008
  4. Jim MeyeringAug 5, 2008

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.