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

Re: Importing all modules in a CVS repo with git-cvsimport

From
Jeff King <peff@peff.net>
Date
Mar 20, 2008, 15:37 UTC
Message-ID
<20080320153728.GA7798@sigill.intra.peff.net>
In-Reply-To
<1206007130.24610.6.camel@pitcairn.cambridgebroadband.com>
On Thu, Mar 20, 2008 at 09:58:50AM +0000, Alex Bennee wrote:
Show 5 quoted lines
> WARNING: file /newcvs/CVSROOT/cvsignore doesn't match strip_path /newcvs/all/. ignoring
> 
> test.cvs is a fresh checkout of the whole tree. "newcvs" is the root of
> CVS on the server. The warnings are the same when I try with "." as the
> module. Or where you saying do this with the actually CVS repo itself?

Hmm. I tested and it worked fine on my system. I'm not sure what you mean by "the CVS repo itself." I actually linked within the $CVSROOT hierarchy. If your version of CVS isn't happy with the symlinks for some reason, you could just munge your cvs hierarchy (assuming you are just doing a one-shot import):

  cd /newcvs
  mkdir all
  for i in `ls | grep -v all | grep -v CVSROOT`; do
      mv $i all
  done
-Peff
Previous: Alex BenneeNext: Robin Rosenberg
Message 6 of 8 in “Importing all modules in a CVS repo with git-cvsimport”
  1. Alex BenneeMar 19, 2008
  2. Daniel BarkalowMar 19, 2008
  3. Alex BenneeMar 20, 2008
  4. Jeff KingMar 19, 2008
  5. Alex BenneeMar 20, 2008
  6. Jeff KingMar 20, 2008
  7. Robin RosenbergMar 20, 2008
  8. Alex BenneeMar 20, 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.