threads / discuss / 17738

git-cvsimport and i18n.commitencoding

Subject: git-cvsimport and i18n.commitencoding

## tl;dr

2 messages between Feb 12, 2009 and Feb 12, 2009.

replies: 1people: 2as markdown or json

Prenom Nom· Feb 12, 2009, 07:01 UTC · lore

Hi, i'd like to import a project from CVS. The cvs commits are done using Cp1252 encoding charset. The thing is i cannot change the .git/config file since the repo is created by git-cvsimport. So how can i use the good charset ?

Johannes Schindelin· Feb 12, 2009, 11:12 UTC · re: Prenom Nom · lore

Re: git-cvsimport and i18n.commitencoding

Hi,
On Thu, 12 Feb 2009, Prenom Nom wrote:
> The thing is i cannot change the .git/config file since the repo is 
> created by git-cvsimport.

Indeed. A dirty little trick would be to edit $(git --exec-path)git-cvsimport and put in your desired changes.

A less ugly solution would be to patch git-cvsimport.perl to add an option --into-existing-repository that does not complain when the Git repository is already initialized, unless the 'origin' branch exists, too.

Hth, Dscho

← back to recent threads