# git-cvsimport and i18n.commitencoding

2 messages from 2009-02-12 to 2009-02-12. Participants: Prenom Nom, Johannes Schindelin.
Thread: https://gitlist.dev/t/17738

## Prenom Nom, 2009-02-12 07:01

Subject: git-cvsimport and i18n.commitencoding
Message-ID: <4993C92E.7080909@yahoo.fr>
URL: https://gitlist.dev/e/4993C92E.7080909%40yahoo.fr

```
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, 2009-02-12 11:12

Subject: Re: git-cvsimport and i18n.commitencoding
Message-ID: <alpine.DEB.1.00.0902121209270.10279@pacific.mpi-cbg.de>
URL: https://gitlist.dev/e/alpine.DEB.1.00.0902121209270.10279%40pacific.mpi-cbg.de
In-Reply-To: <4993C92E.7080909@yahoo.fr>

```
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

```