* Barak A. Pearlmutter <barak@xxxxxxxxxx> [08-07-16 11:09]:
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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
