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

Re: git-cvsexportcommit keyword mismatch issue

From
LNLars Noschinski <lars-2008-1@usenet.noschinski.de>
Date
Jul 16, 2008, 23:16 UTC
Message-ID
<20080716231622.GA5399@lars.home.noschinski.de>
In-Reply-To
<E1KJ30U-0004EL-BV@corti>
* Barak A. Pearlmutter <barak@cs.nuim.ie> [08-07-16 11:09]:
Show 6 quoted lines
>Simply avoiding expanded keywords should solve the problem.  I thought
>git-cvsimport -k would keep them out of my git repo, but no such luck.
>Even when I use "cvs checkout -kk" for the CVS sandbox and then
>"git-cvsimport -k", keywords were *still* expanded in my git repo.
>(This is with both git 1.4.4.4 and git 1.5.6.)  Either the -k switch
>to git-cvsimport is busted, or I'm doing something wrong.
git-cvsimport -k works for me as of version 1.5.5.2 and 1.5.6.2.

In my opinion, git-cvsexportcommit misses an option -k to do cvs update with -kk (as -kk is sticky for already checked out files, but not for the whole repository, so new files will not get -kk set). If I cannot get rid of this cvs repository soon, I'll probably cook up a patch for it.

Previous: Johannes Schindelin
Message 3 of 3 in “git-cvsexportcommit keyword mismatch issue”
  1. Barak A. PearlmutterJul 16, 2008
  2. Johannes SchindelinJul 16, 2008
  3. Lars NoschinskiJul 16, 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.