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

cvsexportcommit and cvsimport's -k option

From
Lars Alexander Noschinski <lars.noschinski@rwth-aachen.de>
Date
Apr 29, 2008, 17:15 UTC
Message-ID
<f6c6e2a5cc39.481773ba@rwth-aachen.de>
[Please CC me on answers, as I'm not subscribed.]
Hello!
Im using git to work on an CVS project. My work cycle is as follows:

... hack away ... git-cvsimport -i -r cvs -kk -v -d $CVSREPOS git-rebase cvs # If work was done in the meantime git-cvsexportcommit -cpuv $COMMIT # Multiple times, if necessary git-cvsimport -i -r cvs -kk -v -d $CVSREPOS git-checkout -b master cvs # commit ids are changed now

As far as I am concerned, this works fairly well, accept when for any reason a line containing a CVS keyword (e.g. $Id$) is contained in a changeset. In this case, patching fails, and I have to investigate why it fails, eventually just copying the old version from the cvs repository.

Would it be possible to add an option to cvsexportcommit to detect such killed keywords and ignore them?

Greetings,
   Lars.
Next: Robin Rosenberg
Message 1 of 3 in “cvsexportcommit and cvsimport's -k option”
  1. Lars Alexander NoschinskiApr 29, 2008
  2. Robin RosenbergApr 29, 2008
  3. Lars NoschinskiMay 2, 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.